[IronPython] Experimental static compilation

Dino Viehland dinov at exchange.microsoft.com
Tue Jun 20 17:27:12 CEST 2006

The reason why we didn't mention it, and the reason why it's disabled by default, is because there are limits to it in what you can do and plenty of corner cases that don't work.  Another way to put that is it's nowhere near passing all the CPython and our own IronPython regression tests (and we have plenty of concerns about how close we can get there).

That being said our CodeDom provider currently enables it by default, and that in turn can be used to create web pages w/ ASP.NET.  So it is at least somewhat functional, but definitely not ready for prime-time.

It currently works by parsing the Python code like we normally do and making lots of guesses about what it sees.  We still generate the various sort of module-initialization code that you'd get w/ Python.  The classes definition becomes the cctor and is run on first access.  And we map all function definitions to returning object & taking all object parameters, unless we detect an overload in which case we pick a virtual method w/ the same name to overload.  Currently it's not very sophisticated in how it does any of this.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of Luis M. Gonzalez
Sent: Tuesday, June 20, 2006 7:05 AM
To: users at lists.ironpython.com
Subject: [IronPython] Experimental static compilation

Hi all,

I see that you added an experimental static compilation in beta 8, which is dissabled by default
However, I didn't find any clue as to how to use it in the documentation...
How does it work?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20060620/575798f2/attachment.html>

More information about the Ironpython-users mailing list