Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24669 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 52389 invoked by uid 1010); 19 Jul 2006 11:13:01 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 52374 invoked from network); 19 Jul 2006 11:13:01 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jul 2006 11:13:01 -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:54346] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 9E/AE-11992-DB31EB44 for ; Wed, 19 Jul 2006 07:13:01 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k6JBCwnM030742; Wed, 19 Jul 2006 13:12:58 +0200 Date: Wed, 19 Jul 2006 13:11:38 +0200 (CEST) X-X-Sender: derick@localhost To: Lukas Smith cc: internals@lists.php.net In-Reply-To: <44B58A36.2010900@php.net> Message-ID: References: <0F.C0.46743.0CB15B44@pb1.pair.com> <44B58A36.2010900@php.net> 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] Re: E_STRICT From: derick@php.net (Derick Rethans) On Thu, 13 Jul 2006, Lukas Smith wrote: > Lukas Smith wrote: > > Ok I see 2 options: > > 1) > > Obviously one solution would be to disallow making anything an E_STRICT > > notice that is not available since the first release of the given major > > version. > > Pierre and Anthony seem to favor this solution. E_STRICT is meant as a tool for us (php developers) to signal possible bad usage of the language and/or possible BC breaks in the future. Therefore it's perfectly valid to require the update of a package in order to be E_STRICT compatible with a later PHP version. I doubt that (for e_strict) there won't be a solution that works on older PHP versions. It is *that* that we need to make sure doesn't happen then and we're in the clear. Derick