Adam Kennedy wrote:
> 2009/4/21 Michael G Schwern <schw...@pobox.com>:
>> I was almost convinced, then I remembered what caused this whole problem.
>> Class::Delegation went from 1.06 to 1.7.1. That's 1.60.0 to 1.7.1 in your
>> system.
>
> Of course that's what it means. The fact you don't have to type the
> last zero is just a convenience...
Of course.
Of course, it could be 1.6.0. Or 1.60.0. Or 1.600.0. Or 1.6000.0. Where
the decimal goes is essentially arbitrary, except most CPAN authors use X.YY
so it makes some sense that it would become X.YY.Z. Only if you're in the
head space of linking the 5.005 -> 5.6.0 conversion to version.pm would you OF
COURSE think that 1.06 becomes 1.060.0. And there's little reason one would.
Therein lies the entire problem. Where the decimal should OF COURSE go is
subjective. Any heuristic which does not acknowledge that is going to
continue to cause user mistakes, no amount of RTFM will make that go away. A
conversion system that mirrors the author's subjective logic will make it go
away.
1.06 -> 1.60.0 does not DWIM. There's no feedback about it until the module
has already been uploaded to PAUSE and then a few weeks later someone points
out the mistake. A warning by the PAUSE indexer would help, but it's still
too late and it still does not DWIM.
--
If you want the truth to stand clear before you, never be for or against.
The struggle between "for" and "against" is the mind's worst disease.
-- Sent-ts'an
