> If you hit F5 and continue execution it should keep on running. You can
> also disable breaking on exceptions via Debug->Exceptions and uncheck the
> "thrown" column for CLR exceptions. It should just be breaking so you can
> look around and seeing what's going on.
>From my naive point of view, I would expect that the process continues
running until (a) I stop/pause it, (b) a breakpoint is hit, or (c) an
exception occurs that would normally stop the program (i.e. propagate
all the way to the top). Not every exception causes execution to
break, e.g. this doesn't:
a = {}
try:
print a[1]
except KeyError:
print "missing"
Although this does (no exceptions when run outside the debugger or
with CPython, of course):
def myiterator():
yield 1
yield 2
raise StopIteration()
for item in myiterator():
print item
What is the distinction here? Is the first considered "user handled"
and the second not, even though it is correctly handled? Is it that
the iteration exceptions always cause the debugger to kick in?
Thanks,
Tony
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
