On Mon, April 20, 2009 10:55 pm, Eric Wilhelm wrote: > # from Yitzchak Scott-Thoennes > # on Monday 20 April 2009 18:53: >>> Form (a) is recommended for all new version numbers. Form (b) is >>> allowed for compatibility with legacy version numbering. >> >> Use a triple tuple if you like, but I want my versions to be a number >> and only a number. >> >> I'm baffled that you would think dictating otherwise makes sense. > > Why does it trouble you to have your floats converted to a tuple in your > META.yml?
I didn't see any "in META.yml" restriction in David's dicta. And I would be very surprised if META.yml publicized a different version than I picked. I could see my version "20090421.001_01" having 20090421.1.1 as a normalized_version or some such for tools that don't have version.pm available, but are we in fact talking about such tools? Even if we are, I wouldn't like to see such a normalized version ever used for anything but comparison. The author decides what the version number is, and that's what should appear when the version is presented as a string. Anything else leads to users having to decide whether something saying x is talking about the same thing labeled y elsewhere.
