[Mono-list] MCS namespaces/Driving MCS in-memory

A Rafael D Teixeira rafaelteixeirabr@hotmail.com
Mon, 17 Sep 2001 14:36:43 -0300

>From: Miguel de Icaza <miguel@ximian.com>

>Ok, I have integrated all of your patches Rafael, they are now in the
>CVS.  I like your namespace solution, I might rename the rest of MCS
>to use Mono.Languages.CSharp later.

In truth I hope to have most of CIR namespace renamed Mono.Languages and 
just have the CSharp's parser and tokenizer living in Mono.Languages.CSharp.

In another front: I've made a first deconstruction/reconstrution effort of 
the driving code (driver.cs), initially to achieve the multiple-languages 
Then I tried to refactor it into a MultiCompiler class that can be called 
from other programs (in that scenario, driver.cs would become just a thin 
parameter-gatherer client of this class). Then I pulled in a interface 
IReportError to be possible to collect errors for the benefit of the 
background compiling on the editor. Then I implemented receiving the source 
code as a string, for already-in-memory situations (the code editor, again).

It's not stable but...

... there's another possibility: System.CodeDom.Compiler. The classes in 
this namespace aren't in the ECMA list, but they are needed for ASP.NET 
on-the-fly compilation of pages, and, I guess, for background compilation on 
the code editor that tags syntax errors as you type.

What do you all think? Which path should we follow, our own tree of classes 
or CodeDom's ?

Rafael Teixeira
Brazilian Developer

Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp