Simon Belak wrote:
> There are two caveats (both trivial to fix) with 2) in my current
implementations. As can be seen above one cannot use decorator syntax
for a recursive error handler definition. I propose changing
error_handler to allow calls without arguments to handle this case.
And second, ff an exception is raised inside the method which handles
it's own errors, a nasty "infinite" loop can ensue. Some stack prodding
should do the trick here.
Submitted patch for the former.
"Infinite loop" turned out to be a non-issue (I was lazy and didn't look
at the code. Sorry for disinformation).
One more thing about error-tossing. With method combination
(before/after, around, next_method) one can inform (call) the
originating method about the error and still have another method do the
view.
Simon
