Thanks for the suggestion =)

That's what I tried first, but then I realized that every time the export list changes in Foo::Core, it has to be updated in Foo::Core::Specialized. That's a less elegant solution than re-implementing Exporter's import within my own, so I opted against it.

every time the export list changes in Foo::Core, it has to be updated in Foo::Core::Specialized.

Why? Why not just initialise F::C::S's EXPORT* vars from F::C's?

package Foo::Core::Specialised;
use Foo::Core ':all';

our @EXPORT = @Foo::Core:@EXPORT;
our @EXPORT_OK = @Foo::Core::EXPORT_OK;
our %EXPORT_TAGS = %Foo::Core::EXPORT_TAGS;

## Add, subtract or overwrite as required.
[download]

That way F::C::S can export everything F::C can unless you explicitly remove it--self maintaining--plus anything you add or overwrite.

---

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP PCW It is as I've been saying!(Audio until 20090817)

Why? Why not just initialise F::C::S's EXPORT* vars from F::C's?

package Foo::Core::Specialised;
use Foo::Core ':all';

our @EXPORT = @Foo::Core:@EXPORT;
our @EXPORT_OK = @Foo::Core::EXPORT_OK;
our %EXPORT_TAGS = %Foo::Core::EXPORT_TAGS;

<b>## Add, subtract or overwrite as required.</b>
[download]

Well, maybe this is the part I don't get. How can I modify the @import list without overwriting the import() function? If I have to overwrite the import() method to be able to modify the args, then the same question applies -- how do I export from F::C?