Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25292 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19193 invoked by uid 1010); 10 Aug 2006 14:38:39 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19178 invoked from network); 10 Aug 2006 14:38:39 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Aug 2006 14:38:39 -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:46877] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 58/25-08715-EE44BD44 for ; Thu, 10 Aug 2006 10:38:39 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.7/8.12.11) with ESMTP id k7AEcVSv020705; Thu, 10 Aug 2006 16:38:32 +0200 Date: Thu, 10 Aug 2006 16:36:59 +0200 (CEST) X-X-Sender: derick@localhost To: Ilia Alshanetsky cc: Michael Walter , internals@lists.php.net In-Reply-To: <1AB5A095-30CB-4B3D-A7B8-5305F566896E@prohost.org> Message-ID: References: <877e9a170608100302n6407821dw5e55187332b74f4f@mail.gmail.com> <3295496D-D427-4C0A-B0FD-393CAA22D4CB@prohost.org> <877e9a170608100635k257e47c8x53b42b52eee0b670@mail.gmail.com> <1AB5A095-30CB-4B3D-A7B8-5305F566896E@prohost.org> 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] Fatal errors From: derick@php.net (Derick Rethans) On Thu, 10 Aug 2006, Ilia Alshanetsky wrote: > > On 10-Aug-06, at 9:35 AM, Michael Walter wrote: > > > What do you feel is incorrect about allowing mentioned errors to be > > handled in userspace? > > My feeling is that errors such as visibility violations should be addressed > during debugging and Q&A phase where simple error logging will be sufficient > to track them. And I feel this is even more true for calling undefined functions or methods... regards, Derick