Generally speaking, I've preferred teaching perl developers a higher level of understanding to catering to lower levels. And, honestly, I find $foo->() eminently more readable than &{ $foo }() anyway.

Of course, the problem I've had with my approach has been getting said developers to want to learn more... which generally tells me how much I want them to continue to work on the code or not. If I had any say in who worked on the perl code, there'd be much higher turnover thus far. The lack of desire to learn, nay, the desire not to learn, would be a huge factor in this.

In reply to Re^4: Subroutines in Dispatch Tables by Tanktalus
in thread Subroutines in Dispatch Tables by Anonymous Monk

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.