[Mono-list] MONO and tooling...

[Miguel de Icaza]

Hello!

> That would not be a good course of action, IMHO, since it means that
> either (1) you are forking the Eclipse sources, or (2) you are depending
> on a proprietry tool to build your source each time, both of which are
> seriously undesirable.

This serves a number of purposes for me though:

	* A big regression test suite for MCS.
	* A big regression test suite for Mono.
	* A chance to fine tune mono to run it at a decent speed.
	* The change to run Eclipse on a full open source platform

Finally:

	* Provide feedback to Microsoft about their JUMP product.
	* Convince Microsoft to open source JUMP ;-)

Since Eclipse has its own toolkit, doing this is a lot easier than doing
a Swing based application.

There are a number of unknowns as you well point out, but the work seems
pretty interesting.  And again, the resulting C# code is pretty damn
good and nice. 

Miguel.