The overloaded function resolution (when IronPython calls .Net) is currently being worked on. You probably read the original code in which IronPython chooses the first callable alternative. The new code does better finds out all methods that can be called and tries to choose the 'best fit'.
This solution is still not perfect because Python's binding ruls are inherently different than for example C#'s and IronPython can still arrive at an ambiguous binding. As of this very moment we are looking into the solution that would allow program(-mer) to pinpoint the very overloaded method to be called. I hope this helps. The code will be available in the upcoming release. Martin > Jonathan Jacobs Wrote: > > Hi, > > I am curious as to how function-overloads plan on being > handled in future versions of IronPython. > > -- > Jonathan _______________________________________________ users-ironpython.com mailing list users-ironpython.com@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
