[IronPython] Two problems

Dan Lash danlash at gmail.com
Fri Aug 13 04:45:14 CEST 2004

I think the problem you're having about the AsyncCallback constructor
is similar to what I was describing in a previous list-email about
some methods arguments' being not so clear in IronPython.

As per the the casting to list: it looks like it must be cast
explicitly to a list if you want to directly access the items in the
list. But you can easily foreach through the "array" without a problem
(if that is what you need to do, which I know it's not, but is worth

>>> import System
>>> for address in
...     print address


On Thu, 12 Aug 2004 17:14:09 -0700, Curt Hagenlocher
<curt at hagenlocher.org> wrote:
> Joao Grilo <grilo at netcabo.pt> 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>
> --
> Curt Hagenlocher
> curt at hagenlocher.org
> _______________________________________________
> users-ironpython.com mailing list
> users-ironpython.com at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com

More information about the Ironpython-users mailing list