in reply to Re^4: Exporter. Correct way to override import? (archaic perldoc)
in thread Exporter. Correct way to override import?

Unfortunately do the perldocs often reflect only an archaic Perl.

Again, not so. Exporter includes 

package YourModule;
use Exporter 'import'; # gives you Exporter's import() method directly
@EXPORT_OK = qw(munge frobnicate);  # symbols to export on request

[download]

Replies are listed 'Best First'.
Re^6: Exporter. Correct way to override import? (archaic perldoc)
by hippo (Archbishop) on May 07, 2018 at 08:53 UTC

    The Exporter POD also includes (in the Good Practices section no less):

    When using Exporter with the standard strict and warnings pragmas, the our keyword is needed to declare the package variables @EXPORT_OK, @EXPORT, @ISA, etc.

      our @ISA = qw(Exporter);
  our @EXPORT_OK = qw(munge frobnicate);

    [download]
[reply]
[d/l]

      So what? Even if it is presented as an option, you should still not pick the version that makes no sense (unless you need compatibility with pre-5.8.3 builds of Perl).

[reply]
Re^6: Exporter. Correct way to override import? (archaic perldoc)
by LanX (Saint) on May 07, 2018 at 00:39 UTC
[reply]

In Section Seekers of Perl Wisdom