[IronPython] IronPython 2.0 Errors...

Curt Hagenlocher curt at hagenlocher.org
Fri Jan 23 17:52:43 CET 2009

Are you familiar with "the halting problem"? :) (

The only reliable way to find if a particular program returns a runtime
error is to execute the program.  For limited, targeted cases, (such as
importing modules) you could write an analyzer program which would be
*often* right -- but I could create a program  that tricks your analyzer
into reporting a problem where none exists.  Consider this:

import sys
sys.modules['foo'] = type(sys)('foo')
import foo

Your static analyzer would have a tough time recognizing that this program
would not raise a runtime error.

On Fri, Jan 23, 2009 at 8:45 AM, António Piteira <
antonio.piteira at wtvision.com> wrote:

>  Hi,
> I'm trying get all runtime errors without actually executing the code. I
> can get all syntax errors using the parser, but runtime errors like "import
> ys" and stuff like that I', not able to.
> Is there any way to do this?
> Thanks,
> Vision
> _______________________________________________
> Users mailing list
> Users at lists.ironpython.com
> http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20090123/2fbfbea8/attachment.html>

More information about the Ironpython-users mailing list