it's a good tool but in my opinion the name 'DIE' is not good, isn't it?
___
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
On Wed, Dec 24, 2008 at 10:29 AM, Curt Hagenlocher wrote:
>
> I don't know whether or not the specific behavior you've identified is a
> bug, but you should definitely enter it into CodePlex so that it can be
> tracked and investigated properly.
>
Oh, sorry -- didn't see that you weren't the orig
On Wed, Dec 24, 2008 at 10:05 AM, Tim Roberts wrote:
>
> But, this has to be considered a rather serious bug, doesn't it? If I
> create an object p2, then insert it into a list at l[0], the Python contract
> guarantees that l[0] and p2 are references to the same object, so that
> modifying one m
On Tue, 23 Dec 2008 21:01:21 +, Michael Foord
wrote:
> Mark Russo wrote:
>
>> In IronPython 2.0, when I replace a Point object in a list using
>> assignment, a copy of the Point object is used to replace the original
>> list element rather than the original Point itself. This does not
>>