| Subject: | Document the consequences of perl5i::latest |
At minimum the user should be informed of the consequences of "use
perl5i::latest". The docs should loudly and clearly state that by using
it they are condemning their code to fail in the future. You can quote
the docs from perl5i::latest. If you're going to hand users a bomb, at
least put warning labels on it.
Any code with "use perl5i::latest" will break at a point in the future.
This is not a theoretical, it is a perl5i feature. Users are not
supposed to be using perl5i::latest. Even for one-offs it makes no
sense, just use the current version of perl5i you have installed
(costing you a grand total of two characters). Optimizing for
perl5i::latest is not just silly, its irresponsible. Its only valid
purpose is for the test suite.
"use perl5i" specifically dies because its the best way get the users
attention and inform them about the backwards incompatibility plan. The
shortest and most obvious path to using perl5i is intended to *not
work*. This is a safety feature. Otherwise folks will not realize
perl5i is doing something different with compatibility. perl5-i exists
to circumvent this safety feature.
I would prefer this module was deleted. Its either keyboard
optimization gone wild or the product of a misunderstanding about how
perl5i works. I don't care how much positive feedback its gotten,
people don't care NOW that it will break their code LATER but boy will
they complain later. And guess who they'll complain to.