Re: RFC 78 (v1) Improved Module Versioning And Searching

[Chaim Frenkel]

I'd put it into 

        Perl::Option{__Package__} 

There was some talk about making Perl:: special. So that might be the one
and only truely global space.

Hmm, that wouldn't work with multiple versions without cooperation.

Alternatively, we could treat a set 

        Perl::Option{FTP::Net}->Debug = 255;

as a method call, and have the package determine it's caller.

<chaim>

>>>>> "BT" == Bennett Todd <[EMAIL PROTECTED]> writes:

BT> If the only real problem that can be found with making module use
BT> package-local is in these few option-flag type variables, perhaps
BT> they could be handled differently. E.g. suppose normal package
BT> variables end up being local to the package that "use"-es the
BT> package, and when a package actually wants to make a genuine global
BT> for all users of the package, it explicitly tucks it into a variable
BT> whose name starts with main::. E.g. let Net/FTP.pm post its debug
BT> flag into $main::Net::FTP::Debug, and the list of exception classes
BT> requested of Fatal.pm could be posted into @main::Fatal.

-- 
Chaim Frenkel                                        Nonlinear Knowledge, Inc.
[EMAIL PROTECTED]                                               +1-718-236-0183