Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24378 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 47261 invoked by uid 1010); 14 Jul 2006 14:29:33 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 47239 invoked from network); 14 Jul 2006 14:29:33 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jul 2006 14:29:33 -0000 X-PHP-List-Original-Sender: sean@caedmon.net X-Host-Fingerprint: 69.60.120.90 iconoclast.caedmon.net Linux 2.4/2.6 Received: from ([69.60.120.90:56572] helo=iconoclast.caedmon.net) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 6D/A9-41830-B4AA7B44 for ; Fri, 14 Jul 2006 10:29:32 -0400 Received: from localhost ([127.0.0.1]) by iconoclast.caedmon.net with esmtp (Exim 3.35 #1 (Debian)) id 1G1OeR-00070T-00; Fri, 14 Jul 2006 10:28:20 -0400 Message-ID: <44B7AA42.9060305@caedmon.net> Date: Fri, 14 Jul 2006 10:29:22 -0400 User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Ilia Alshanetsky CC: Lukas Smith , internals@lists.php.net References: <0F.C0.46743.0CB15B44@pb1.pair.com> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] E_STRICT From: sean@caedmon.net (Sean Coates) 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. S