Assume that your first idea is wrong, and try to think through the various options. I think that the biggest mistake people make is latching onto the first idea that comes to them and trying to do that. -- Larry Wall ---------------------------------------------------------------- From: Xxx_Xxxxx@xxxx.xxx To: ... CC: perl5-porters list , ... Subject: Re: change Perl's version-searching behavior? Yyyyyy Yyyyyyy Sun, 15 Apr 2001 22:42:46 +0300 (EET DST) > Perl has no reliable way to know the version of a module before > loading it, Hmm ... that _is_ bad. How about package ; or must Perl load all or nothing of a file? FWIW, Xxx_Xxxxx@xxxx.xxx ---------------------------------------------------------------- To: Xxx_Xxxxx@xxxx.xxx cc: ..., perl5-porters list , ... Subject: Re: change Perl's version-searching behavior? From: Zzzz Zzzzz Zzzzzzz > Yyyyyy Yyyyyyy Sun, 15 Apr 2001 22:42:46 +0300 (EET DST) > > Perl has no reliable way to know the version of a module before > > loading it, > > Hmm ... that _is_ bad. How about > > package ; It seems to me that if you wanted to do this, it would be much simpler and more reliable to adopt the convention that version 1.23 of Foo::Bar resides in the file Foo/Bar-1.23.pm For example, it renders the following question irrelevant: > or must Perl load all or nothing of a file? It also allows multiple versions of the same module to coexist, which your scheme doesn't.