I would say that if you have a module explicitly calling functions in the main package, your module is not modular at all! If the "global" function is needed everywhere, it should be in a separate module, importable by the other modules. Or if a module needs another package (let's say the main package) to provide it with a function, perhaps it would be cleaner if main sent a reference instead: 

package main;

Bar::bar(\&foo);

sub foo {
  # do stuff
}

package Bar;

sub bar {
  # need to call a subroutine provided by the caller
  my $subref = shift;
  $subref->();
}

[download]

The only uses I have had for &sub are to generate subroutine references and to override subroutine prototypes.

In reply to Re: To & or not to & ? by itub
in thread To & or not to & ? by DrWhy

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.