IronPython mangles names. For example:
def method():
return 1
Produces:
public static object method$f0()
The test_prefix would get therefore preserved so on a second thought, this may
work, provided that nunit executes public static methods and doesn't require
specific return value. Ours is always "object" in this case.
Martin
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of William Reade
Sent: Thursday, December 08, 2005 10:02 AM
To: Discussion of IronPython
Subject: Re: [IronPython] NUnit with IronPython
Does this mean that IronPython will emit methods, but their names will be
mangled, or that it simply won't produce anything that can be effectively used
from outside?
William
Martin Maly wrote:
>This is, sadly, true. IronPython will not preserve the name of the method as
>we know it...
>
>Martin
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Keith J.
>Farmer
>Sent: Thursday, December 08, 2005 9:46 AM
>To: Discussion of IronPython
>Subject: Re: [IronPython] NUnit with IronPython
>
>For backwards compatibility, NUnit would also accept method names beginning
>with "test" ("test_" ?). However, I don't think IP emits methods as we know
>them yet?
>
>-----
>Keith J. Farmer // [EMAIL PROTECTED]
>
>
_______________________________________________
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
