Can no longer dbcont after error

[LachlanA]

Greetings all,

I usually run with  debug_on_error(1).  It used to be possible to  dbcont 
after an error (usually also continuing through a string of consequent
errors), which was extremely useful.  In my case, I load and pre-process a
big chunk of data, and then process each record independently.  Even though
the iteration with the error will be corrupted, I could continue through the
other data looking for more bugs without redoing all of the pre-processing.

It seems dbcont no longer works after an error (like it doesn't on Matlab). 
I have two questions:

a) Is that likely to be a consequence of using exceptions to handle errors?
b) If so, would it be possible to restore the ability to continue? 
Obviously the continuation would have skipped the execution of some code,
but even given that, it is useful to be able to continue from the next
statement.

If people agree that the old behaviour should be restored, but no-one knows
off hand how to, I'll add that to my to-do list :)

Thanks,
Lachlan



--
View this message in context: 
http://octave.1599824.n4.nabble.com/Can-no-longer-dbcont-after-error-tp4673748.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.