Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25176 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63423 invoked by uid 1010); 3 Aug 2006 09:31:49 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 63407 invoked from network); 3 Aug 2006 09:31:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Aug 2006 09:31:49 -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:52076] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 41/D3-44390-382C1D44 for ; Thu, 03 Aug 2006 05:31:48 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k739Vel3000959; Thu, 3 Aug 2006 11:31:40 +0200 Date: Thu, 3 Aug 2006 11:31:27 +0200 (CEST) X-X-Sender: derick@localhost To: Richard Quadling cc: Lukas Smith , PHP Developers Mailing List In-Reply-To: <10845a340608030225k38b8bab6i7720bf3c8c9bbc11@mail.gmail.com> Message-ID: References: <7.0.1.0.2.20060803104541.0853b1e0@zend.com> <20060803095558.49c4e484@pierre-u64> <44D1B055.5070905@php.net> <44D1B505.1010300@php.net> <10845a340608030205rd012a71g30a97a3f4d2f7bc8@mail.gmail.com> <10845a340608030225k38b8bab6i7720bf3c8c9bbc11@mail.gmail.com> 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: rethink OO inheritance strictness From: derick@php.net (Derick Rethans) On Thu, 3 Aug 2006, Richard Quadling wrote: > On 03/08/06, Derick Rethans wrote: > > On Thu, 3 Aug 2006, Richard Quadling wrote: > > > > > The issue this brings is toggling E_STRICT on and off at RUNTIME > > > required? (I suspect that would be a LOT of work). > > > > It's only an issue for the first script that is opened... not for > > includes. As the parsing E_STRICT things work fine.... but only *after* > > the file has been executed. In this example the included file will never > > throw e_Strict errors for example: > > > > > error_reporting(0); > > include 'included.php'; > > ?> > > > > Aha. So, if I use an __autoloader, I COULD be clever and place my > "loose" classes in 1 directory and my "strict" classes in another. The > autoloader would search for the class and set the error_reporting > level appropriately before including/requiring. Yeah, that would work. Derick