I appreciate your original suggestion and your bringing the focus to bear on 'first principles'. I understand and support the principle of cohesion.

We may differ on the application of that principle to this case. I submit that "give me a value or tell me why you failed" is sufficiently cohesive and a useful job description for a subroutine. Granted, it is not Functional Cohesion in the strictest sense. But I think it is a common, intuitive, and effective way to foster clear program flow at the level of the call.

I agree with your comment on btrott's submission and have /msg'ed him to say so. Since my app is already OO, it is the approach I intend to use in this case.

But not every program is OO and I was simply wanting to build on your very helpful suggestion and see if it might be possible to extend that idea to allow a useful return value while factoring out the wrapper subroutine.

My question (and it's about time for me to stop yacking and run some test scripts) is whether the   eval {die "error description"}   trick will work and allow me to access $@ back at the call level.

Thanks again for this exchange. David

In reply to Re: Re(5): Idomatic Handling of Subroutine Error by dvergin
in thread Idomatic Handling of Subroutine Error by dvergin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.