I was using a module Project::Config without problems, which had this structure:

package Project::Config;
use warnings FATAL => qw(all);
use strict;
use Exporter;
our @ISA='Exporter';
our @EXPORT_OK=qw(....);
...
sub AUTOLOAD {...}
INIT {...}
[download]

In one application, I wanted to replace the

use Project::Conifg;
[download]

by an explicit BEGIN { require .... import .... } sequence, and I wrote it like this:

package MyApp;
use strict;
use warnings;

# This had worked before:
# use Project::Config qw(foo bar);

# New code which does not work:
BEGIN {
  require 'Project/Config.pm';
  Project::Config::import(qw(foo bar));
}
[download]

It turned out that the call of the import function triggered Project::Config::AUTOLOAD(), i.e. as if no import were defined. I had expected that by compiling Config.pm, the Exporter would inject an import() method. Any idea why this failed?

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.