Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23815 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 79899 invoked by uid 1010); 31 May 2006 07:46:53 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 79884 invoked from network); 31 May 2006 07:46:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 May 2006 07:46:53 -0000 X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:48394] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id D6/25-07504-9E94D744 for ; Wed, 31 May 2006 03:46:49 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k4V7kkvD005895; Wed, 31 May 2006 09:46:46 +0200 Date: Wed, 31 May 2006 09:46:22 +0200 (CEST) X-X-Sender: derick@localhost To: Marcus Boerger cc: internals@lists.php.net In-Reply-To: <649570026.20060531004803@marcus-boerger.de> Message-ID: References: <649570026.20060531004803@marcus-boerger.de> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] [RFC] E_STRICT From: derick@php.net (Derick Rethans) On Wed, 31 May 2006, Marcus Boerger wrote: > right 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: > > 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 > > > 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. regards, Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org