Re: [RFC] E_STRICT
| From: | Antony Dovgal | Date: | Wed, 31 May 2006 14:24:35 +0000 |
| Subject: | Re: [RFC] E_STRICT | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-23827@lists.php.net to get a copy of this message | ||
On 31.05.2006 11:46, Derick Rethans wrote:
On Wed, 31 May 2006, Marcus Boerger wrote:Yes. So that E_STRICT notices introduced in 6.x will become E_FATALs only in 7.0 and so on. -- Wbr, Antony Dovgalright now the fate of E_STRICT error messages is uncertain. A few people think those should change to fatal after a reasonable amount of time, is two years (e.g. 5.0.0) reasonable. A few even think a minor version like 5.1 to 5.2 is enough but the majortiy (at least i guess so) wants the change only on a major version change like 5.0 to 6.0. Currently the manual says: <manual> 2048 E_STRICT (integer) Run-time notices. Enable to have PHP suggest changes to your code which will ensure the best interoperability and forward compatibility of your code. since PHP 5 </manual> So the RFC goes: Extend the manual to specify that issues reported by E_STRICT messages are most likely to become fatal errors in the next major version.I would say so, as long as we define major version as "6.0" here.