[IronPython] Writing new modules

Keith J. Farmer kfarmer at thuban.org
Tue Aug 17 22:33:15 CEST 2004

Of course, I mean this to describe a similar situation to the Managed C++ compiler -- it can take the same source, and target either the managed or unmanaged world.  IronPython could take source and target either CLR or CPython, with marshalling performed as needed.
If IronPython could easily wrap managed assemblies, that would be a good trick as well, and solve the problem of dealing with non-trivial types.


From: users-ironpython.com-bounces at lists.ironpython.com on behalf of Keith J. Farmer
Sent: Tue 8/17/2004 2:28 AM

be to create a thin marshalling layer that allows the IL/bytecode to
internally use whatever, if necessary (a smart compiler could detect if
the type could be replaced outright), while exposing only the CLR or
Python type expected by the target environment.

More information about the Ironpython-users mailing list