Actually, I'm wondering about the usefulness of an assembly delimiter for the import statement. IE, instead of clr.Add*, you have something more like: from (FooAssembly, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089) import * This maintains the from/import structure in current use -- it just expands the type that the first argument can handle to include, instead of a python library identifier, an assembly reference. It'd be easier to parse, I think, when dealing with the whole IronPython->Assembly path, rather than hunting for scattered clr.Add* references.
________________________________ From: [EMAIL PROTECTED] on behalf of Martin Maly Sent: Wed 1/4/2006 9:41 AM To: Discussion of IronPython Subject: Re: [IronPython] Some new bugs with asssembly loading... The reason is that clr.References is a tuple without improved formatting. Using tuple was a way to get the idea out there and gather feedback and experiences. Ultimately we may use some custom written tuple-like structure.
<<winmail.dat>>
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
