Re: [RFC] E_DEPRECATED
| From: | Richard Quadling | Date: | Tue, 24 Oct 2006 12:44:19 +0000 |
| Subject: | Re: [RFC] E_DEPRECATED | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26225@lists.php.net to get a copy of this message | ||
On 24/10/06, Lukas Kahwe Smith <lsmith@php.net> wrote:
Richard Quadling wrote: +1 - As an aside, it would be extremely useful to have the PEAR classes marked as NON strict (in some way) until they are. I know this is outside of the core, but using E_STRICT already means you have to toggle off E_STRICT for PEAR. MAYBE STRICT (e.g. strict class PEAR {...}) as a new keyword for a class, just so that you know that it IS strict (or at least expecting to be). heh .. no that would not be useful .. it would be lying. PEAR already has decided on an RFC that will mandate PHP5 only for new packages soon. Also PEAR mandates E_STRICT compliance for PHP5 only packages. So time will fix this issue.Ah. Oh. Excellent. Didn't know that. Thank you. (Balancing ... balancing ...) -- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!"