Linked by Thom Holwerda on Thu 19th Nov 2009 15:29 UTC, submitted by AlexandreAM
Microsoft "Microsoft, which has been pursuing concurrent improvements for its Visual Basic and C# programming languages, plans to open up compilers for the languages and add capabilities for asynchronous programming and immutability. Discussed at the Microsoft Professional Developers Conference in Los Angeles, the blueprint for the two languages will feature compilers as services and accommodations for multicore processors, said Luca Bolognese, program manager for the languages group at Microsoft."
Thread beginning with comment 395598
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: ...
by TommyCarlier on Fri 20th Nov 2009 07:35 UTC in reply to "..."
Member since:

What it means is that they've rewritten the C#-compiler in C# and the VB-compiler in VB, as .NET libraries, which you'll be able to use in your own application. You'll get access to the parsed AST for analysis (and probably also modification).

Reply Parent Score: 1

RE[2]: ...
by memson on Fri 20th Nov 2009 11:50 in reply to "RE: ..."
memson Member since:

The compiler services are already part of the .Net core libraries. You can already compile assemblies and executables on the fly - I have even done this to implement a sandboxed scripting service for a product we have. All of the ASP.Net stuff uses the compilers in this way if you do not pre-compile them.

Reply Parent Score: 2

RE[3]: ...
by TommyCarlier on Fri 20th Nov 2009 11:57 in reply to "RE[2]: ..."
TommyCarlier Member since:

Sure, you can compile source code to .NET assemblies, but that just calls the native compiler (source file(s) -> assembly file). The new compiler-as-a-service gives you access to the AST in memory. You'll be able to use the official parser for C#/VB instead of writing your own, if you need to analyze source code (or modify the AST before compiling it down to MSIL).

Reply Parent Score: 1