On Thu, Mar 02, 2006 at 15:13:07 +0200, Zohar Kelrich wrote:
> We were discussing some confusing macro behaviours, when we came upon this
> curious thing. This code is really simple in p5, as it doesn't really have
> separate compilation, but in p6, the modules can be pre- compiled or cached.
>
One way to think of your macro example (instead of the ->import one,
which is harder to define, i think):
Every time you use a module it's used by the compiler, and by the
emitted code.
The compiler loads the macros, the emitted code loads the non-macro
stuff.
Since the clsoure is created in the
We were discussing some confusing macro behaviours, when we came upon
this curious thing. This code is really simple in p5, as it doesn't
really have separate compilation, but in p6, the modules can be pre-
compiled or cached.
8<--
module ImportHeadache;
my $m;
sub im
