Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24668 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 50191 invoked by uid 1010); 19 Jul 2006 11:10:06 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 50174 invoked from network); 19 Jul 2006 11:10:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 19 Jul 2006 11:10:06 -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:54514] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id ED/6E-11992-C031EB44 for ; Wed, 19 Jul 2006 07:10:05 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k6JB9wwI032210; Wed, 19 Jul 2006 13:09:58 +0200 Date: Wed, 19 Jul 2006 13:08:38 +0200 (CEST) X-X-Sender: derick@localhost To: Greg Beaver cc: Sean Coates , internals@lists.php.net In-Reply-To: <44B82F69.8080808@php.net> Message-ID: References: <0F.C0.46743.0CB15B44@pb1.pair.com> <44B7AA42.9060305@caedmon.net> <44B82F69.8080808@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] E_STRICT From: derick@php.net (Derick Rethans) On Fri, 14 Jul 2006, Greg Beaver wrote: > Sean Coates wrote: > > Ilia Alshanetsky wrote: > > > >>Why not just define your own custom error handler and have it filter out > >>the error messages that you don't want to see... To me this would seem > >>like a easier approach, i would be against adding a in-language filter > >>for this. > > > > > > Inability to easily determine which errors come from which version of > > PHP (in userspace, or otherwise) aside, E_STRICT can't always be handled > > at runtime. > > > > I can't think of a situation in 5.1.x where this is the case, but in > > 5.0.x, the use of 'var' (instead of public|private|protected) caused an > > E_STRICT at compile-time: before a userspace error handler could have > > been registered. > > > > ... admittedly, this is abnormal, but I think we should keep it in mind > > anyway. > > This is not entirely accurate. A userspace error handler can catch > E_STRICT during parsing of included files and eval(). This is how we > make install-pear-nozlib.phar work with our PHP 4/5 compatible PEAR files. Only if it is not in the main PHP script though. Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org