Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80680
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4NpJxuuqc-wTr1aE4K+wZBT8+04j+9-SsY+nhUMU83fDUg@mail.gmail.com>
References: <CAFMT4NpJxuuqc-wTr1aE4K+wZBT8+04j+9-SsY+nhUMU83fDUg@mail.gmail.com>
Date: Sat, 17 Jan 2015 06:54:33 +0100
Message-ID: <CAEZPtU7NxhLQUkQN3ryOaipMZ5A9hBW9E4SzstMYJcDua0jFVQ@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Wed, Nov 19, 2014 at 12:11 AM, Levi Morrison <levim@php.net> wrote:
> Dear Internals,
>
> I am proposing an RFC[1] to remove PHP 4 constructors in PHP 7. If
> accepted, methods with the same name as their defining class will no
> longer be recognized as constructors. As noted in the RFC, there are
> already many situations where we do not recognize these methods as
> constructors, such as in namespaces and traits and when `function
> __construct` is also present.
>
> Andrea Faulds has kindly written a utility that identifies when a PHP
> 4 constructor is defined[2]. It does not automatically change the code
> for liability reasons. The utility PHPMD[3] can also detect this but
> has a false positive when `__construct` is also defined.

Not much to say about it as it is a taste/yes/no thing.

Let wait the required period and move to vote, I do not see much needs
to argue in a circular way forever :)

Cheers,
-- 
Pierre

@pierrejoye | http://www.libgd.org