Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78996
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.214.178 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20141119143329.GX2294@phcomp.co.uk>
References: <CAFMT4NpJxuuqc-wTr1aE4K+wZBT8+04j+9-SsY+nhUMU83fDUg@mail.gmail.com>
	<546C9E22.6090301@fedoraproject.org>
	<20141119134632.GV2294@phcomp.co.uk>
	<546CA8C0.1060707@gmail.com>
	<20141119143329.GX2294@phcomp.co.uk>
Date: Wed, 19 Nov 2014 16:36:32 +0200
Message-ID: <CAPhkiZxteVW+H57iBAemwDpqH0JzqkvLo8eVQAga3SXOLom+zg@mail.gmail.com>
To: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors
From: narf@devilix.net (Andrey Andreev)

Hi,

On Wed, Nov 19, 2014 at 4:33 PM, Alain Williams <addw@phcomp.co.uk> wrote:
> On Wed, Nov 19, 2014 at 02:27:12PM +0000, Rowan Collins wrote:
>
>> PEAR is not a single organisation who can mass update all the
>> modules; the guidelines could be updated, if they haven't been
>> already, but there would still be a whole repository full of
>> libraries which used this.
>>
>> Now, whether that's acceptable or not, I don't know, but it does
>> highlight the size of the compatibility break.
>
> How many servers are stuck on PHP 4 ?
>
> Of those 'stuck' servers, how many have applications still under active
> development ?
>
> The point is: how many people would get annoyed if PEAR stopped supporting PHP 4 ?
>
> IMHO: making PHP 5.3+ the PEAR baseline would not seem unreasonable.

Nope. The point is, how much of that code *depends on PHP4-style
constructors*, which work perfectly fine in PHP 5.x.

Regardless, it's time to put it in the past, so a +1 from me for this RFC.

Cheers,
Andrey.