Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:23798 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90158 invoked by uid 1010); 30 May 2006 22:45:59 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 90143 invoked from network); 30 May 2006 22:45:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 May 2006 22:45:59 -0000 X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:47695] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 7B/3E-07504-62BCC744 for ; Tue, 30 May 2006 18:45:59 -0400 Received: from baumbart.mbo (dslb-084-063-066-070.pools.arcor-ip.net [84.63.66.70]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 27DDC35C1EB for ; Wed, 31 May 2006 00:45:55 +0200 (CEST) Date: Wed, 31 May 2006 00:48:03 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <649570026.20060531004803@marcus-boerger.de> To: internals@lists.php.net MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [RFC] E_STRICT From: helly@php.net (Marcus Boerger) Hello internals, 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. RFC = Comments? Comment from myself: To have this working we need tests. For a start we need tests that trigger any E_STRICT present in php/zend c code. It might as well halp to turn on E_STRICT in E_ALL but oh , i say no more. Best regards, Marcus