IronPython can consume CLS types and extend them, but cannot produce new CLS types. Unfortunately that last part is extremely tricky because CLR types are not dynamic, but Python types are. It is something that's on our radar but we don't yet have a solution for it.
Do you want to help develop Dynamic languages on CLR? (http://members.microsoft.com/careers/search/details.aspx?JobID=6D4754DE-11F0-45DF-8B78-DC1B43134038) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Mechlenborg Sent: Tuesday, February 28, 2006 9:04 AM To: users@lists.ironpython.com Subject: [IronPython] CLS compliance Hi I'm trying to find out how well CLR enables language interoperability for dynamic languages, and in that connection I have been looking a bit on IronPython (IP). Using Google and searching the archives of this mailing list, I get the impression that IP is capable of both consuming and producing CLS compliant code, is this correct? If so, I would be very interested in information describing how to do this as a programmer and also how it has been implemented. Does any such information exist? If any of you know of any sources that discuss language interoperability for other dynamic languages, I would also be interested in these. Kind regards, -- Peter _______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ users mailing list users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
