When speaking of OO methods, you wrote:
> 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
> exception in Perl, and eval is a long way from a try block.
Have you tried using a custom Perl solution for this? Graham
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. :)
You might also take a look at Exception::Class, a base exception
class on which you can base any exceptions your system wishes
You also wrote:
> Worse, perl's sub routine simplicity of having subroutines
> take a variable number of arguments ...
Have you ever looked at Class::MultiMethods
? It might help
you in this area, if you like that sort of structured stuff. :)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||