--- "Brett W. McCoy" <[EMAIL PROTECTED]> wrote:
> > Not to correct those smarter and more knowledgeable, I'd like to
> > call a rephrase on that one. =o)
> > my() makes a variable lexical, meaning it isn't in any package.
> > packages equate to namespaces, which mean little or nothing to
> > lexicals, who live and die in terms of scope.
>
> Good call. How specifically does code in a require get evaluated?
> According to the require manpage, it does a "do 'filename.pl' with
> some code wrapped around it to check @INC and make sure it hasn't
> already been included. According to the do manpage, code evaluated
> with do cannot see lexicals in the enclosing scope. So,
specifically,
> how do lexical variables get affected in a require?
>From the little testing I've done and the logic I can wrangle (since I
can't recall a location for documentation just now), every file *is* a
scope block. A lexical in one file can't be accessed by code in another
file unless explicitly passed.
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
