# from David Golden
# on Tuesday 21 April 2009 13:34:
>Because perldelta implies that v-strings aren't supposed to be used
>for version numbers. It's pretty explicit for Perl version numbers
>and even has a warning for 'use v5.10'.
v-string in use/require is non-portable
Perl will warn you against potential backwards compatibility
problems with the "use VERSION" syntax.
>If the warning were extended to modules (e.g. 'use Foo::Bar v1.2'),
That would be sick and wrong. The warning in 'use v5.6.1' makes some
sense because it will result in garbledygook error messages in ancient
(obsolete, nobody uses them anymore, why are we ever discussing it?)
perls.
A warning in a module version number doesn't make sense unless you just
want to make things difficult.
>then I'd be even more supportive of saying that v-strings and
>version.pm have nothing to do with each other and any problems are
>just user-error. :-)
Whatever. I look forward to some mechanism which is anywhere nearly as
efficient and convenient as '$VERSION = v1.2.1;' and 'use foo v1.2.1'.
I think the whole "use version; $VERSION = qv('v1.2.1');" business is
utter tedium for no advantage.
--Eric
--
Anyone who has the power to make you believe absurdities has the power
to make you commit injustices.
--Voltaire
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
