I appreciate your tactic and I can understand it.
But it's confusing for me to ignore $@'s contents, I have some Python and C++ background so I prefer to create objects not messages. What if your object's method or object calls eval in somebody's exception handler code but it's not yours?
In reply to Re^4: 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: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |