Menu
Back at the PDC in 2008, in the C# futures talk by Anders Hejlsberg he talked about rewriting the C# compiler and providing a "compiler as a service" I certainly got the impression at the time that they were targeting the C# 4.0 timeframe for this....
Well, does anyone know what the state of this is? it doesn't seem to be there in the CTP and there is almost no information on the WEB apart from links to the 2008 PDC session video (roughly an hour in).
Has this initiative gone dark?
550
C-states are states when the CPU has reduced or turned off selected functions. Different processors support different numbers of C-states in which various parts of the CPU are turned off.
C-states are idle power saving states, in contrast to P-states, which are execution power saving states. During a P-state, the processor is still executing instructions, whereas during a C-state (other than C0), the processor is idle, meaning that nothing is executing.
C-states are numbered starting with C0 (the shallowest state where the core is totally awake and executing instructions) and go to C6 (the deepest idle state where a core is powered off). P-states control the desired performance (in CPU frequency) from a core.
Certainly not C# 4.0. We are just finishing up the last few bug fixes for C# 4.0.
This direction for the toolset is the long term plan, and might never come to fruition. And I don't discuss schedules for unannounced, hypothetical future features.
We have just shipped a preview release of "compiler as a service" aka the "Roslyn" project.
We are still not announcing the final ship vehicle; it will be post Visual Studio 11.
184
It's already available in Mono for quite some time.
27
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
