Hello. It's me again. Sorry for late reply.
I said about other languages just to clarify my expectations from exception handling mechanism I'll choose after discussing this topic with you and other monks.
All I want is to have as close as possible exception handling strategy with objects as errors and backtraces printing to STDERR when error cannot be handled by application. Also I want to avoid all pitfalls related with language peculiarities and consider all possible edge cases, This is for elaboration best common strategy for handling exceptions in Python style (or C++), or, better, as in languages with built-in exception system on language level. I know Perl has it too by in its own way.
Here is code which fails one of the tests on pre-5.14 versions.
It's one of pitfalls I want to avoid. Maybe I overlooked some other pitfalls, All I want is to take into consideration all possible pitfalls like this.
In reply to Re^6: Best practices for handling exceptions in die/eval style
by krautcat
in thread Best practices for handling exceptions in die/eval style
by krautcat
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |