Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re: Exception Classes Advice on Subclasses

by venk (Acolyte)
on Dec 21, 2005 at 13:39 UTC ( #518302=note: print w/replies, xml ) Need Help??

in reply to Exception Classes Advice on Subclasses

I suggest using subclasses rather than trying to differentiate your exceptions through 'fields'.
if ( my $e = X::Class::SubClass1->caught ) { # handle } elsif ( my $e = X::Class::SubClass2->caught ) { # handle }
In each block, the above code directly describes the type of error that it handles --- I think using 'fields' requires the reader to work a little harder to understand what is going on. That said, I recommend not getting carried away with defining complex exception hierarchies. Start with a simple X::Class->caught and subclass only as required by your application.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://518302]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (12)
As of 2016-10-21 17:47 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (289 votes). Check out past polls.