E_STRICT -> E_STRICT + E_DEPRECATED [was: Re: [PHP-DEV] RfC: rethink OO inheritance strictness]
| From: | Sebastian Bergmann | Date: | Thu, 03 Aug 2006 09:47:22 +0000 |
| Subject: | E_STRICT -> E_STRICT + E_DEPRECATED [was: Re: [PHP-DEV] RfC: rethink OO inheritance strictness] | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25181@lists.php.net to get a copy of this message | ||
Christian Schneider wrote:
> But like you I prefer the E_STRICT version without modifying the
> language though. But I'm sharing Lukas' concern about the definition of
> E_STRICT: Is it to be changed to E_ERROR at some point? Otherwise
> E_NOTICE would be more appropriate IMHO.
Not that I am advocating this, but one solution could be splitting
E_STRICT into E_STRICT and E_DEPRECATED for the respective meanings.
--
Sebastian Bergmann http://www.sebastian-bergmann.de/
GnuPG Key: 0xB85B5D69 / 27A7 2B14 09E4 98CD 6277 0E5B 6867 C514 B85B 5D69