'break' Causes Execution of Procedure?
Scott Brady Drummonds
scott.b.drummonds.nospam at intel.com
Wed Aug 11 13:32:21 EDT 2004
"Scott Brady Drummonds" <scott.b.drummonds.nospam at intel.com> wrote in
message news:cfdif9$hhm$1 at news01.intel.com...
> How is it possible that the call to 'break' is seemingly being replaced
with
> a call to 'main'?
I should also point out that the second time that the program's execution
reaches the 'break' statement in the 'main' procedure, I get the following
cryptic error message:
<quote>
DEBUG: advancing both simulators to 20178
DEBUG: encountered EOFError; breaking loop
XXX lineno: 109, opcode: 0
Traceback (most recent call last):
File "test.py", line 135, in ?
main(sys.argv[1])
File "test.py", line 109, in main
break
SystemError: unknown opcode
</quote>
What's going on here?
Scott
--
Remove .nospam from my e-mail address to mail me.
More information about the Python-list
mailing list