Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:78980
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.181 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
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: Wed, 19 Nov 2014 13:15:30 +0900
Message-ID: <CAGa2bXZp9UeDsn7MZPJJjiq5SuN_qdP6NVfEPHqDa2LmC6b9gQ@mail.gmail.com>
To: Levi Morrison <levim@php.net>
Cc: internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=bcaec5161acdb8389605082e78c9
Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

--bcaec5161acdb8389605082e78c9
Content-Type: text/plain; charset=UTF-8

Hi all,

On Wed, Nov 19, 2014 at 8:11 AM, Levi Morrison <levim@php.net> wrote:

> 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.
>

No reason to keep old constructor for PHP7. IMHO.
+1 for removing it PHP7, announce depreciation now.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net

--bcaec5161acdb8389605082e78c9--