Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:65481
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.187 cause and error)
Message-ID: <5108ECF1.4080401@lsces.co.uk>
Date: Wed, 30 Jan 2013 09:50:41 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <op.wq746rv5idpuyk@damnation.nl.lo.geleia.net>
In-Reply-To: <op.wq746rv5idpuyk@damnation.nl.lo.geleia.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE] Deprecate and remove calls from incompatible
 context
From: lester@lsces.co.uk (Lester Caine)

Gustavo Lopes wrote:
> I've opened the vote for the "remove calls from incompatible context" RFC:
>
> https://wiki.php.net/rfc/incompat_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 ?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk