I've always just abstracted general-purpose code like this into a utility module (or modules, as makes sense). For example, I use an updated version of the module in RFC: Log::Painless to handle common logging, and subs look like this: 

sub foo {
   trace enter;  #logs entry into the sub if loglevel is 'trace'
   eval {
      sub_that_might_die(shift @_);
   };
   if ($@) {
      debug caught; #logs catching of exception if loglevel is 'debug'
      warn $@;
      return;
   }
   trace leave; #logs departure from sub if loglevel is 'trace'
}

[download]

Yes, it's still repetitive to type trace enter at the top of each sub, but no more so than using attributes, and I find it's very natural. I don't know if a similar approach would address all your "cross-cutting concerns", but I thought I'd throw it out there as a possibility.

Good luck... and let us know what you decide and why, I'm curious. ;-)

<–radiant.matrix–>
A collection of thoughts and links from the minds of geeks
The Code that can be seen is not the true Code
I haven't found a problem yet that can't be solved by a well-placed trebuchet

In reply to Re: Subroutine attributes for solving crosscutting problems by radiantmatrix
in thread Subroutine attributes for solving crosscutting problems by friedo

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.