Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80640
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
Sender: stelian.mocanita@gmail.com
In-Reply-To: <alpine.DEB.2.11.1501161126340.4080@whisky.home.derickrethans.nl>
References: <CAFMT4NpJxuuqc-wTr1aE4K+wZBT8+04j+9-SsY+nhUMU83fDUg@mail.gmail.com>
	<0DD30A0D-E7CA-4150-83E0-8FD46635279C@ajf.me>
	<CAFMT4Nq1X0bONCs=TJyjB1vZ=+UEnX0L8pSex5fWfUMssh4ktQ@mail.gmail.com>
	<alpine.DEB.2.11.1501161126340.4080@whisky.home.derickrethans.nl>
Date: Fri, 16 Jan 2015 13:54:40 +0100
Message-ID: <CAMc0WS7MjJ85BTSQcRZtGS5MU_9_DfU95SRh6qkmDgWkS2dO4w@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Levi Morrison <levim@php.net>, Andrea Faulds <ajf@ajf.me>, internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1133af6acf9b23050cc479fb
Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors
From: stelianm@php.net (Stelian Mocanita)

--001a1133af6acf9b23050cc479fb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello everyone,

Might I suggest community feedback on this one in a reddit thread? My guess
is that even though a lot of applications out there are still PHP 4 ctor
reliant, a very low percentage of these applications might be under active
development.

Best,
Stelian

On Fri, Jan 16, 2015 at 12:28 PM, Derick Rethans <derick@php.net> wrote:

> On Thu, 15 Jan 2015, Levi Morrison wrote:
>
> > On Thu, Jan 15, 2015 at 9:55 AM, Andrea Faulds <ajf@ajf.me> wrote:
> > >
> > > Upon further thought, I=E2=80=99m not super-enthusiastic about this. =
As has
> > > been pointed out, it=E2=80=99s a pretty serious BC break, whether cod=
e can
> > > be automatically updated or not. PHP 4 constructors may be obsolete,
> > > but an awful lot of code uses them.
> > >
> > > A better solution, IMO, might be simply to add a deprecation notice.
> > > This would make it obvious during development if you=E2=80=99ve accid=
entally
> > > defined a PHP4 constructor, and would encourage migration away from
> > > them, but wouldn=E2=80=99t prevent existing code from working.
> >
> > Possibly. The reality of my position is that I am unhappy about our
> > current constructor situation. Having `__construct` and only
> > half-heartedly supporting old-style constructors for the next several
> > years (maybe ten?) does not sound good at all.
> >
> > Removing one of the constructors is a nicer end product than fully
> > supporting both, in my opinion, which is why I proposed dropping it.
>
> Instead of just dropping it, which would likely generate odd bugs,
> declaring an old style constructor should *tell* you it's no longer
> working- perhaps with as strong of an error as an
> E_COMPILE_ERROR=E2=80=94atleast for PHP 7. Just removing it support would=
, IMO,
> be silly.
>
> cheers,
> Derick
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>

--001a1133af6acf9b23050cc479fb--