Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79029
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.215.10 cause and error)
Message-ID: <1416476628.15061.4.camel@kuechenschabe>
To: Alain Williams <addw@phcomp.co.uk>
Cc: internals@lists.php.net
Date: Thu, 20 Nov 2014 10:43:48 +0100
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>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Wed, 2014-11-19 at 14:33 +0000, Alain Williams wrote:
> 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 ?

The point about breaking this is *not* PHP 4 compatibility but
compatibility between PECL packages. The name of the constructor method
is part of the API.

Think about code like this in module A:

   class A_class {
       function A_class() { }
   }

and then module B extending this:

   class B_class  extends A_class {
       function B_class() {
           A_class();
       }
   }

I also wonder how Andrea's tool handles more indirect cases (C_class
extends B_class, while B_class has no ctor so C_class calls directly
A_class's ctor)

So I'm -1 on this.

johannes