[IronPython] IronPython v2.0 Alpha 3 Released!

[Dino Viehland]

The two DLRs shipped between IronPython and IronRuby are about 1 day apart - so they should almost be identical.  We did bump the version on the IronPython release so they're not actually drop-in replacements for each other.
Currently evaluation mode needs to be flipped on and it's a rather global option (-X:FastEval at the command line if you want to play with it although it's not yet exactly "fast").  It will disable its self when it detects it can't handle a certain construct (currently that's generator functions).  I'm not sure what the balance will end up being on whether we'll have hints or if we'll try and detect it or a combination of both.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Keith J. Farmer
Sent: Thursday, July 26, 2007 6:56 PM
To: Discussion of IronPython
Subject: Re: [IronPython] IronPython v2.0 Alpha 3 Released!

Is this DLR compatible with IronRuby's?

Also, below you mention different paths for code execution.  Does the DLR analyze the code to make that determination, or is there a way we can hint the runtime to say "This code block can be interpreted."?

________________________________
From: users-bounces at lists.ironpython.com on behalf of Dino Viehland
Sent: Thu 7/26/2007 5:13 PM
To: Discussion of IronPython
Subject: [IronPython] IronPython v2.0 Alpha 3 Released!
This release also contains near complete support for evaluation support.  There are now only a handful of corner cases where evaluation support is incomplete.  Evaluation support enables the DLR to interpret code instead of compiling it and executing it resulting in faster run times for code that is executed once or rarely executed at all.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20070726/8a5fcd6b/attachment.html>