in reply to Re: Re: Re:: Adam:: Re:: OO-style question
in thread OO-style question
Have you tried using a custom Perl solution for this? Graham Barr's Error module (direct doc link) lets you use standard try and catch semantics for exception handling. I've not used it, because I've always just stuck w/ eval, because it works for me. :)> They need to be able to throw named exceptions which the > caller can choose to catch or not. die is the closest thing to a +n > exception in Perl, and eval is a long way from a try block.
You might also take a look at Exception::Class, a base exception class on which you can base any exceptions your system wishes to throw.
You also wrote:
Have you ever looked at Class::MultiMethods? It might help you in this area, if you like that sort of structured stuff. :)> Worse, perl's sub routine simplicity of having subroutines > take a variable number of arguments ...
|
---|