Kris Craig wrote:
*raises his hand*
1.01 and 1.0.1 are essentially the same thing. If a versioning model
doesn't utilize the second dot (many don't), then 1.01 would be the same as
1.0.1 in a project that does use it.
The Gitflow model reserves that last digit for hotfixes. However, many
developers (including myself) drop the second dot as it's pretty much
superfluous. Maybe that's an American thing, I dunno. But having 1.1 ==
1.01 would cause this function to be completely and utterly *worthless *for
many developers like myself.
Sorry Kris, but the version number system that PHP uses by definition is three
numbers. We are currently on 5.4.x and the function is defined as
"version_compare() compares two "PHP-standardized" version number strings"
so as far as I am concerned most of this discussion has been irrelevant.
The comment posted to the page is equally in error as only one of the strings
are in what I would call "PHP-standardized". But the main point here is that the
function is DESIGNED to allow us to enable and disabled PHP actions based on the
version number of PHP, so as long as the version numbers are correctly set IN
PHP then there is nothing wrong with the function? Redefining a function to do a
job it is not defined for is simply wrong and if you want a function that works
for a different versioning system, then it's a new function!
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
