[IronPython] Some new bugs with asssembly loading...
Martin.Maly at microsoft.com
Wed Jan 4 09:41:09 PST 2006
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.
From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of J. Merrill
Sent: Wednesday, January 04, 2006 8:51 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Some new bugs with asssembly loading...
What is causing clr.References to display without any obvious separation of the info for the different assemblies? Shouldn't its ToString make it more clear that there are three different assemblies, e.g. with something like
(mscorlib, Version=188.8.131.52, Culture=neutral, PublicKeyToken=b77a5c561934e089), (System, Version=184.108.40.206, Culture=neutral, PublicKeyToken=b77a5c561934e089), (c.d.e, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null)
(using ",<newline>" as the separator). The way things are, it's certainly not obvious how many assemblies there are in the output. (The first few times I looked at this, I totally missed that System was in there at all!)
At 07:31 PM 1/3/2006, Martin Maly wrote (in part)
>>>> import clr
>(mscorlib, Version=220.127.116.11, Culture=neutral,
>PublicKeyToken=b77a5c561934e089, System, Version=18.104.22.168,
>Culture=neutral, PublicKeyToken=b77a5c561934e089, c.d.e,
>Version=0.0.0.0, Culture=neutral, PublicKeyToken=null) [snip]
J. Merrill / Analytical Software Corp
users mailing list
users at lists.ironpython.com
More information about the users