[IronPython] Two problems

Paolo Molaro lupus at ximian.com
Thu Aug 19 20:29:54 CEST 2004

On 08/12/04 Jim Hugunin wrote:
> > 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.

This bug was fixed in mono cvs in July:

The other bug I think is IronPython not selecting the right method to
execute based on the passed arguments when there are overloads.

I guess people may be also interested in performance progresses:
current mono from cvs is about 50% slower than CPython on parrotbench
(excluding the infamous b5 bench): used to be 2x slower as reported in
Jim's slides. b5 times improved, too: we are now 10 times slower instead
of 70x (this is all due to exception handling so relatively unimportant
in the real world). Expect more improvements in the future as well.


lupus at debian.org                                     debian/rules
lupus at ximian.com                             Monkeys do it better

More information about the Ironpython-users mailing list