The CLR Compiler Geek Roundtable | TheChannel9Team

littleguru
<3 Seattle

Nice video. I like the guy from Australia, who has written the compiler book.

Charles
Welcome Change

You'll see more customer/MS people interaction videos on C9 in the future.

Glad you liked it!

C

littleguru
<3 Seattle

I was thinking to buy the book, since I'm very interested in compiler and the IL. I guess after reading the book I know a lot more about what's going on internally in the JIT and IL.

If I don't write a compiler at least it gives me a lot internals... that's also a big benefit.

lassebjerreknudsen
lassebjerreknudsen

I didn't get the title of the book, anyone can point my in the right direction?

rhm

If the CLR team wants ideas for improvements how about making code unloadable/gc-able so that programs that generate code on the fly don't leak memory. Yes, you can use Appdomains now, but there is unacceptible marshalling overhead with that approach in programs that have a high number of calls to generated code.

rhm

Notice to everyone:-

STOP POSTING LONG LINKS!!!!!!

It screws up the page formatting. Thankyou.

TM

rhm wrote:
If the CLR team wants ideas for improvements how about making code unloadable/gc-able so that programs that generate code on the fly don't leak memory. Yes, you can use Appdomains now, but there is unacceptible marshalling overhead with that approach in programs that have a high number of calls to generated code.

See Lightweight Code Generation in .NET 2.0 (DynamicMethod class particularly). I think that is want you suggest.

dantheman82

Interesting topic and discussion. Yes, the fundamental switch to partial classes for one thing seems a little counterintuitive (unless if you are used to C++ header files and cpp
files that flesh out the implementation).

The whole discussion by the guy from Australia about private types is not really correct. Using .NET reflection, I can access private data members and functions during
runtime. And using the .NET Reflector (or similar), I can access private data inside DLL or EXE files with not too much difficulty. So, the whole
private/protected/public distinction (while interesting when it comes to correctness) is not really practical in managed code.

Of course, interfacing between languages is definitely much easier. And while we're discussing languages, why not have a true Java language compiler that
"just works" (like the PHP compiler Phalanger) in the CLR? I'm talking JButton, not Button, and so on...so that I can run Java applet code in a Winform UI. Gabeesh?

P.S. trueguru, not only did you screw up the layout of the page by incorrectly posting the link, but you did so because you shamelessly had to include a referral
link for the book.

rhm

TM wrote:

See Lightweight Code Generation in .NET 2.0 (DynamicMethod class particularly). I think that is want you suggest.

Thanks for the headsup. It sounds interesting although I can't read the docs on it now (the online MSDN library being next-to useless). I'll take a look when I get the Whidbey beta.