Re^2: Do you use an exception class in your Perl programs? Why or why not?

I've been mostly underwhelmed with exception based techniques and exception objects. Try::Tiny has resolved many of my complaints with exceptions in general, so I am using them again.

It bothers me to have to keep writing the likes of:

 
if( $@ =~ /some error stuff/ ) {
    warn "error stuff occurred";
} 
else { 
    warn "some other message" ;
}
[download]

An exception class system that works would remove the need for parsing data out of strings that should be available in a data structure.

I feel like Perl exceptions are kind of like Perl OO in general. The language provides a bare minimum set of features that can be used to get things done, bat can also be extended in clever ways.

We have 37 million Class::Foo modules that tried to build a better Perl object system. After years of experimentation, Moose hit the scene and has taken over.

Is exception handling in Perl ripe for the introduction of a revolutionary module like Moose? What would it look like?

Thanks for your thoughts.

TGI says moo

Comment on Re^2: Do you use an exception class in your Perl programs? Why or why not? Download Code

Replies are listed 'Best First'.

Re^3: Do you use an exception class in your Perl programs? Why or why not?
by zwon (Abbot) on Mar 14, 2010 at 10:14 UTC

if( $@ =~ /some error stuff/ ) { warn "error stuff occurred"; } else { warn "some other message" ; }
[download]

As I said I usually just do

if($@) { Oops; }
[download]

$@

I feel like Perl exceptions are kind of like Perl OO in general.

$@

[reply]
[d/l]
[select]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks