Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61583
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.176 as permitted sender)
Message-ID: <5009DA26.9020603@gmail.com>
Date: Sat, 21 Jul 2012 00:22:30 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: internals@lists.php.net
References: <CADqTB_jrj__c-1d=F2zuK_Rj4J_HpXkrqPgA3J57Nxi7WBTBTg@mail.gmail.com> <CAN+gjSdiyD=BTJyoYYuwxyJLiBD-45-bzRWw9HoYRXjCOSRX3A@mail.gmail.com> <5009C8AA.10603@sugarcrm.com>
In-Reply-To: <5009C8AA.10603@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] common issue with version_compare()
From: hartmut.holzgraefe@gmail.com (Hartmut Holzgraefe)

On 07/20/2012 11:07 PM, Stas Malyshev wrote:
> 1.0.0 and 1.0 are different things. If you want to make a comparison
> that takes into account only two components, you can just cut them both
> to two components, then compare.

it is hart to imagine a 1.0 followed by 1.0.0 in real world, but
the only reason for something like this that i can come up with
is that, for whatever reason, a project wants to change from
two component version numbers to three component ones right after
having done a 1.0. And in that case a 1.0.0 following the 1.0
would be a new release, even if it only differs by the extra .0

And so 1.0 < 1.0.0 would be perfectly correct.

-- 
hartmut