[IronPython] shall #14454 be fixed for 1.X ?

Dino Viehland dinov at exchange.microsoft.com
Tue Apr 22 17:31:22 CEST 2008

If you’re really stuck you could port the beta 2 event handling code back to 1.x and run against your own private build - at least until we do 1.1.2 – I’m not yet sure when we’ll do that but I’ll make sure we discuss it this week.  It’s not super straight forward, because we now hook each delegate independently to the object which enables this to work, but it’s not too bad either.  ReflectedMembers.cs in ReflectedEvent.InPlaceAdd would  be the place to start looking in 1.x and ReflectedEvent.cs again in ReflectedEvent.InPlaceAdd would be the 2.x side of things.

From: users-bounces at lists.ironpython.com [mailto:users-bounces at lists.ironpython.com] On Behalf Of ????????
Sent: Tuesday, April 22, 2008 4:41 AM
To: Discussion of IronPython
Subject: Re: [IronPython] shall #14454 be fixed for 1.X ?

Note that you can 'fix' this yourself by unsubscribing from events when
you have finished with them.

I've spend my whold today doing what you've mentioned without any success yet.
The framework I based on depends heavily on a really complicate event sequences
that I can hardly comprehend.

Perhaps, tomorrow I'll have a better luck.

Msg sent via @Mail Softnix Messaging Server http://www.softnix.co.th
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20080422/e1b37db5/attachment.html>

More information about the Ironpython-users mailing list