[IronPython] IP 2.0 and DLR

[Dino Viehland]

These shared modules are for consumption from one dynamic language to another.  So for example in Python I could do "import foo".  Today IronPython v1.x falls back to looking at .NET assemblies to find namespaces if a Python module/package isn't found.  In v2.0 we'll also fall back to the DLR module loader which might return say a module which was created from JavaScript or Ruby or another language.

Unfortunately there's still no support for early-bound access to Python classes.

________________________________________
From: users-bounces at lists.ironpython.com [users-bounces at lists.ironpython.com] On Behalf Of Lyle Thompson [LThompson at ixiacom.com]
Sent: Monday, April 30, 2007 10:26 AM
To: users at lists.ironpython.com
Subject: [IronPython] IP 2.0 and DLR

Great news on IP 2.0!

Could I get a little clarification on the DLR?

" and provides a shared module for consuming those languages from
applications."

Is that the same as allowing consumption of IP assemblies from
non-dynamic assemblies (e.g. C#)? Or will we still need to
write/generate delegate wrappers around IP assemblies to consume them?

Thanks,
Lyle
_______________________________________________
users mailing list
users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com