[IronPython] Two problems

Jim Hugunin jim at ironpython.com
Fri Aug 13 06:30:15 CEST 2004


Curt Hagenlocher wrote:
> Joao Grilo writes:
> 
> > print """Runs up to this point"""
> > asyncAccept = socket.BeginAccept(System.AsyncCallback
> (callbackFunction), socket)
> > print """This won't show at all, due to a core dump"""
> 
> For what it's worth, Microsoft's 1.1 CLR raises an exception
> at this point:
>      bad args to this method <constructor# for System.AsyncCallback>

This shows a bug in both IronPython and Mono.  The fact that there is a mono
bug is obvious.  Managed code shouldn't be able to cause a core dump.  The
CLR 1.1 response is better.  You should report this to the mono team if
possible.

The IronPython bug is that delegate constructors don't work right in this
release.  As Thane pointed out in an earlier email, simple delegates in
IronPython are supposed to be created automatically, i.e.
"socket.BeginAccept(callbackFunction, socket)'.

The big bug in IronPython-0.6 is that even this won't work as the created
delegate won't have the right signature.  You can see Ops.GetDelegate if
you're interested in the really weak code that's breaking for you.

-Jim





More information about the Ironpython-users mailing list