in reply to
Be more OO with "Class" modules?
I wasn't being clear. I don't mean OO modules in general. I meant Error or Errors or Exception::Class like that in particular.
Could you please explain your reasoning? I'm not disagreeing with you per se, just curious as to why.
Memory leaks.... Building a Large-scale E-commerce Site with Apache and mod_perl
The reasons to avoid try/catch have already been discussed on the thread perrin mentioned.
A Programming Language, 1962
Programming the 1900 series in COBOL, 1974
Algorithms + Data Structures = Programs, 1976
The C Programming Language, 1978
System V - Interface definition, 1986
Z80 Assembly Language Programming, 1979
TheSOURCE User's Manual, 1979
The C Primer, 1983
Interactive Fortran 77, A Hands on Approach, 1984
Perl.1 man page, 1991
Results (70 votes),