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 );

[download]

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.

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

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.