Subject: | Why does $Foo::VERSION imply package Foo? |
Date: | Fri, 7 Jun 2013 15:45:07 -0700 |
To: | bug-Module-Metadata [...] rt.cpan.org |
From: | Jeffrey Ryan Thalhammer <jeff [...] imaginative-software.com> |
If Module::Metadata sees a fully qualified VERSION variable...
$Foo::Bar::VERSION = 1.23;
...then it claims the file provides a package called Foo::Bar, even if no such package was actually declared in the file.
That behavior seems dubious to me. Can you help me understand the rationale for it? Here's the relevant line of code:
https://metacpan.org/source/BOBTFISH/Module-Metadata-1.000014/lib/Module/Metadata.pm#L589
Thanks for your time.
-Jeff