Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61648
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.42 as permitted sender)
Message-ID: <500D6DDF.3070308@gmail.com>
Date: Mon, 23 Jul 2012 17:29:35 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: Kris Craig <kris.craig@gmail.com>
CC: Andrew Faulds <ajfweb@googlemail.com>, 
 Tjerk Meesters <tjerk.meesters@gmail.com>,
 "internals@lists.php.net" <internals@lists.php.net>, 
 Rasmus Schultz <rasmus@mindplay.dk>
References: <CADqTB_jrj__c-1d=F2zuK_Rj4J_HpXkrqPgA3J57Nxi7WBTBTg@mail.gmail.com> <CAN+gjSdiyD=BTJyoYYuwxyJLiBD-45-bzRWw9HoYRXjCOSRX3A@mail.gmail.com> <5009C8AA.10603@sugarcrm.com> <CADqTB_i8b39JXnNnv=ZUtrXBBup8f+jafhuEntgCU3CpQGSSxA@mail.gmail.com> <CAKOpQSx9GqieXx0W4vgWu_3=Am97EsHjRTi7HOcLCvERcqD4RQ@mail.gmail.com> <A78EE73B-C81A-401D-812E-ED23FE8A47C1@gmail.com> <CAN+gjScgcqo+VHFpGps75tkAyU6kX5bfwt5oq5qzMxdqZMFXVA@mail.gmail.com> <CAKOpQSxS57xMV9bzO7N_H1jQZWfUoqM_hPzbWb51yHvdxA5ZRQ@mail.gmail.com>
In-Reply-To: <CAKOpQSxS57xMV9bzO7N_H1jQZWfUoqM_hPzbWb51yHvdxA5ZRQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] common issue with version_compare()
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 22/07/12 04:08, Kris Craig wrote:
> On Sat, Jul 21, 2012 at 3:09 AM, Andrew Faulds <ajfweb@googlemail.com>wrote:
>
>> If you think 1.1 =/= 1.01 you're sure using some weird version numbers.
>> Only 1.0.1 would be smaller.
>>
>> Has anyone seen these weird version ordering schemes in practise? On any
>> major projects of note?
>>
>>
> *raises his hand*
>
> 1.01 and 1.0.1 are essentially the same thing. 
No, it is not.

> 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.
It's the first time I hear about a project writing 1.0.1 as 1.01

> 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.

It doesn't matter that you bump the minor or revision number, it's up to
each
project what should increase on a change of X severity. It would still
work flawlesslly
as far as you do it consistently.
If you release 1.0.1, 1.02, 1.0.3 and expect it to order that way, it
will fail. And I guess
that so would many developers too.