Think about Loose Coupling | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
Caveat: I've never used Exception::Class in anger, so take my comment with a grain of salt. I think the main point of using different subclasses is that you can check for the subclass directly when 'catch'ing the exception, and handle it appropriately to the type of error encountered. For example
Sure, you could set up something similar with using a single MyException subclass and testing the contents, but it seems a lot cleaner this way. Update: Heh, adrianh answered the question before my post made it. Oh well, take my post as a more extended example :-) Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan In reply to Re: Exception Classes Advice on Subclasses
by tirwhan
|
|