Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65482
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.177 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5108ECF1.4080401@lsces.co.uk>
References: <op.wq746rv5idpuyk@damnation.nl.lo.geleia.net>
	<5108ECF1.4080401@lsces.co.uk>
Date: Wed, 30 Jan 2013 11:07:39 +0100
Message-ID: <CAH-PCH69SQEzXA5QxV4_OnoY7AB1vKJezB0mQJDBiPLH77mYUw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=14dae93406652f6f0504d47eaed3
Subject: Re: [PHP-DEV] [VOTE] Deprecate and remove calls from incompatible context
From: tyra3l@gmail.com (Ferenc Kovacs)

--14dae93406652f6f0504d47eaed3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 30, 2013 at 10:50 AM, Lester Caine <lester@lsces.co.uk> wrote:

> Gustavo Lopes wrote:
>
>> I've opened the vote for the "remove calls from incompatible context" RF=
C:
>>
>> https://wiki.php.net/rfc/**incompat_ctx#vote<https://wiki.php.net/rfc/in=
compat_ctx#vote>
>>
>
> FINALLY realised why this was an itch I had to scratch.
> Why just pick on one aspect of E_STRICT ? Surely the end point should be
> removing all of the 'advisory warnings' blocked by E_STRICT rather than
> having a vote on each one.
>
> Flag as depricated ready to be removed in PHP6. So the discussion SHOULD
> be on what else should be removed in PHP6 ?


as I mentioned before in another thread back in the pre 5.3 days E_STRICT
was indeed used in some cases for the same purposes as what E_DEPRECATED
does now, but there are exceptions so these should be reviewed case by case
basis for deprecation/removal instead of replacing every E_STRICT with
E_DEPRECATED.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--14dae93406652f6f0504d47eaed3--