X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fc-sharp;h=ddf6844701f73790dda4c60efec685c56f340860;hb=96f27584e01d9f73f9e810872f6c96608371261a;hp=8faf5f83b1335925c0e1518baeabcaeae73a19f8;hpb=ab7465ea46961ce33b982d9bea33a7a462a78072;p=mono.git

diff --git a/web/c-sharp b/web/c-sharp
index 8faf5f83b13..ddf6844701f 100644
--- a/web/c-sharp
+++ b/web/c-sharp
@@ -1,20 +1,28 @@
 * MCS: The Ximian C# compiler
 
-	MCS is currently able to compile itself and many more C#
-	programs (there is a test suite included that you can use).
+	The Mono C# compiler is considered feature complete at this
+	point and relatively mature.  MCS is able to compile itself
+	and many more C# programs (there is a test suite included that
+	you can use).  It is routinely used to compile Mono, roughly
+	half a million lines of C# code.
 
-	We are in feature completion mode right now.  There are still
-	a couple of areas that are not covered by the Mono compiler, but
-	they are very very few at this point.
+* Pending tasks
 
-	MCS was able to parse itself on April 2001, MCS compiled itself
-	for the first time on December 28 2001.  MCS became self hosting
-	on January 3rd, 2001. 
+	There are a few known bugs in the Mono C# compiler, but
+	they are very very few at this point,
+	you can also browse the MCS <a href="http://bugzilla.ximian.com/buglist.cgi?product=Mono%2FMCS&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time&form_name=query">bugs</a> from Bugzilla.
 
 	A test suite is maintained to track the progress of
 	the compiler and various programs are routinely compiled and
 	ran.
 
+** Slides
+
+	Slides for the Mono C# Compiler presentation at .NET ONE are
+	available <a
+	href="http://primates.ximian.com/~miguel/slides-europe-nov-2002/Mono_C_Sharp_Overview_1007.sxi">here</a>
+	in StarOffice format.
+
 ** Obtaining MCS
 
 	The Mono C# compiler is part of the `mcs' module in the Mono CVS
@@ -23,10 +31,9 @@
 
 ** Running MCS
 
-	MCS is written in C# and uses heavily the .NET APIs.  At this point
-	MCS only runs on Windows with the .NET Framework SDK installed.  Work
-	is progressing rapidly in our JIT engine and our class libraries to
-	allow MCS to be ran in non-Windows systems. 
+	MCS is written in C# and uses heavily the .NET APIs.  MCS runs
+	on Linux with the Mono runtime and on Windows with both the
+	.NET runtime and the Mono runtime.
 
 ** Reporting Bugs in MCS
 
@@ -73,36 +80,42 @@
 
 		* Code generation: The code generation is done through
 		  the System.Reflection.Emit API.
-
 	</ul>
 
-<a name="tasks">
-** Current pending tasks
+** CIL Optimizations.
 
-	Simple tasks:
+	The compiler performs a number of simple optimizations on its input:
+	constant folding (this is required by the C# language spec) and 
+	can perform dead code elimination.
 
-	<ul>
-		* Redo the way we deal with built-in operators.
-	</ul>
+	Other more interesting optimizations like hoisting are not possible
+	at this point since the compiler output at this point does not
+	generate an intermediate representation that is suitable to
+	perform basic block computation.  
 
-	Larger tasks:
-	<ul>
+	Adding an intermediate layer to enable the basic block
+	computation to the compiler should be a simple task, but we
+	are considering having a generic CIL optimizer.  Since all the
+	information that is required to perform basic block-based
+	optimizations is available at the CIL level, we might just skip
+	this step altogether and have just a generic IL optimizer that
+	would perform hoisting on arbitrary CIL programs, not only
+	those produced by MCS.  
 
-		* Jay does not work correctly with `error'
-		  productions, making parser errors hard to point.  It
-		  would be best to port the Bison-To-Java compiler to
-		  become Bison-to-C# compiler. 
-		  
-		  Nick Drochak has started a project on SourceForge for this.
-		  You can find the project at: <a href="http://sourceforge.net/projects/jb2csharp/">
-		  http://sourceforge.net/projects/jb2csharp/</a>
+	If this tool is further expanded to perform constant folding
+	(not needed for our C# compiler, as it is already in there)
+	and dead code elimination, other compiler authors might be
+	able to use this generic CIL optimizer in their projects
+	reducing their time to develop a production compiler. 
 
-		* Semantic Analysis: Return path coverage and
-		  initialization before use coverage are two great
-		  features of C# that help reduce the number of bugs
-		  in applications.  It is one interesting hack.
+** History
 
-	</ul>
+	MCS was able to parse itself on April 2001, MCS compiled itself
+	for the first time on December 28 2001.  MCS became self hosting
+	on January 3rd, 2002. 
+
+	The Mono Runtime and the Mono execution engine were able to make
+	our compiler self hosting on March 12, 2002.
 
 ** Questions and Answers