Approach 3, if indeed it is supposed to read...

sub print_notice { print 'please be sure that XXX is installed first' } print_notice;

...is a no-no in my book. It does two things, it defines a scalar, and prints it out. In my experience, sooner or later you will want to grab that string, to feed it to split or lc, and you will be out of luck, because the damned thing will get printed to STDOUT.

That leaves approaches 1 and 2. Approach 2 gets my nod, because if the worst comes to the worst, you can always set a breakpoint in the sub (or add some debug print) and find out from whence it is being called. And, as is alluded to elsewhere, it lends itself to i18n and l10n.

--
g r i n d e r

In reply to Re: print_notice or print $notice or print notice? by grinder
in thread print_notice or print $notice or print notice? by princepawn

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.