bothersome we could add it to the 1.1.1 bug list, but in
> the meantime I'd suggest the workaround Michael mentioned (wrapping the args
> up in the tuple)
>
> Cheers,
> John
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] On Beh
ut in the
meantime I'd suggest the workaround Michael mentioned (wrapping the args up in
the tuple)
Cheers,
John
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eric Rochester
Sent: Monday, July 30, 2007 1:37 PM
To: IronPython Users
Subject: [IronP
Thanks, Michael, that will work.
It seems blindingly obvious now, but I hadn't even considered it, since I
generally try to pass CLR types to CLR methods.
Sheepishly,
Eric
On 7/30/07, Michael Foord <[EMAIL PROTECTED]> wrote:
>
> Hello Eric,
>
> Interestingly it works with:
> pc = ParamCall(('a',
Hello Eric,
Interestingly it works with:
pc = ParamCall(('a', 'b', 'c'))
passing a tuple instead of an array.
Still looks like a bug.
Michael
http://www.ironpython.info/
Eric Rochester wrote:
> Hi,
>
> I've been using IronPython for a few months now, and I'm really
> enjoying it. Thanks for a
Hi,
I've been using IronPython for a few months now, and I'm really enjoying it.
Thanks for all the hard work that's gone into it.
I recently ran across an issue, and I wondered if anyone else has seen it. I
think it's probably a bug, but I couldn't find a bug report, either.
Basically, if there
