==================================================================
> This RFC proposes a minimal efficient well-scaling mechanism for
exporting.
> Only export of subroutines and tags are supported by this
mechanism.
>
Though I'm not completely sure how the implementation works in other
compiled languages, I rather like the C, Java, Python method where
just about everything can be exported / imported.
==================================================================
This proposal is about making a *minimal* efficient API for
exporting. If you want something more complicated, you may/should
use Export::Heavy @whatever;
==================================================================
Namely, why not make the built-in importer allow symbol
export. Namely, move and optimize the perl-based Exporter code into C
code.
==================================================================
I see no point in discussing what is core and what is a module *now*.
Nobody said that what
use module @foo;
is doing is not done in the core. All you need is to define
module::import as an XSUB, and populate $INC{module}.
[The other part of your message mixes export and autoloading, I do not
understand its relevance to the discussion at hand.]
Ilya
