Actually, let me take that back. This issue still exists, but only repros on my 32bit box locally. I'd just quickly tried it on my 64bit box before and we have been fixing some issues like this. It's unclear to me why that would matter in this case.
Sorry for the false info. I'll get that filed for us... -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ryan Dawson Sent: Monday, August 14, 2006 11:38 AM To: [EMAIL PROTECTED]; Discussion of IronPython; Discussion of IronPython Subject: Re: [IronPython] critical code generation issue? We've been doing some bug fixing in the area of exception blocks lately. It looks like we got this case as it does not repro on the very latest sources (which are available on CodePlex). Thanks for the report though, keep them coming. -Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Timothy Fitz Sent: Monday, August 14, 2006 11:01 AM To: Discussion of IronPython Subject: [IronPython] critical code generation issue? Can someone else confirm these results: IronPython 1.0.60725 on .NET 2.0.50727.42 Copyright (c) Microsoft Corporation. All rights reserved. >>> def test(): ... try: ... raise Exception() ... except: ... for n in range(10): ... break ... return 1911 ... >>> print test() None Under CPython this should print 1911. _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
