in reply to (bbfu) (just to confuse the issue) Re(2): use strict and exporting package variables
in thread use strict and exporting package variables

FYI, Exporter can't do that since its code is in a different file and therefore has no access to the lexical variables in your module's file.

        - tye (but my friends call me "Tye")
  • Comment on (tye)Re: (bbfu) (just to confuse the issue) Re(2): use strict and exporting package variables

Replies are listed 'Best First'.
(bbfu) (Re(2): tye) (just to confuse the issue) Re(2): use strict and exporting package variables
by bbfu (Curate) on May 01, 2001 at 10:30 UTC

    I know that. :-P

    What I was thinking of, though I didn't actually say it, was some sort of mechanism where you would pass it a reference to a lexical variable that it would then export into the caller's symbol table. I can't think of any reason that would be useful (and it kinda defeats the whole point of having package lexicals, anyway) except as an insane way of (not) avoiding the use vars syntax. :-)

    use strict; my $family; my @jewels; use base qw(Exporter); use vars qw(@EXPORT @EXPORT_LEXICALS); @EXPORT = qw( foo bar $blah ); @EXPORT_LEXICALS = ( \$family, \@jewels );

    Man, that's just sick. ;-p

    bbfu
    Seasons don't fear The Reaper.
    Nor do the wind, the sun, and the rain.
    We can be like they are.