| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
Having use 5.whatever imply use compat::perl5 would be a start, at least. But it wouldn't be a 100% solution because a lot of code doesn't bother to specify a Perl version.
IMO, the most straightforward solution seems to be to add an empty compat::perl5 module to the core Perl 5 distribution (and on CPAN), so that Perl 5 will recognize use compat::perl5 as a valid statement, but one which doesn't actually do anything. | [reply] [Watch: Dir/Any] [d/l] [select] |
This was about upgrading code which runs equally well on P5 and P7.
So manually adding a simple use 5... would solve this.
use compat::Perl5 is IMHO thought to be an automated flag introduced by P7 at compile time when downloading modules from CPAN
without P7 meta tag.
I don't think using it explicitly is a good idea, this would only add to more confusion.
use 5... is far easier to understand and works out of the box on all older P5 installations.
It would be nice to see a formal RFC and a test suite covering all disputed edge cases.
| [reply] [Watch: Dir/Any] [d/l] [select] |