Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41961 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68848 invoked from network); 17 Nov 2008 09:51:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Nov 2008 09:51:21 -0000 X-Host-Fingerprint: 134.130.78.10 unknown Received: from [134.130.78.10] ([134.130.78.10:24044] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 83/82-53741-89E31294 for ; Mon, 17 Nov 2008 04:51:21 -0500 Message-ID: <83.82.53741.89E31294@pb1.pair.com> To: internals@lists.php.net Date: Mon, 17 Nov 2008 10:51:18 +0100 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Thunderbird/1.5.0.7 Mnenhy/0.7.4.666 MIME-Version: 1.0 References: <28.8E.39815.8C421294@pb1.pair.com> <2dedb8a0811170016i74ce2faepef092a1302920202@mail.gmail.com> In-Reply-To: <2dedb8a0811170016i74ce2faepef092a1302920202@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Posted-By: 134.130.78.10 Subject: Re: [PHP-DEV] Fatal error: Call to a member function on a non-object From: christopher.vogt@rwth-aachen.de (Christopher Vogt) Hi Kalle, > I personally don't really mind it, as you got the instanceof and > typehinting to check for whenever a variable is an object, so I would > say its more of a user design issue. Fatal errors just requires you to > refactor your code so your code shouldn't emit such things which I'm > alright with. fatal error can also happen caused by a bug. The case described in my Mail is even rather likely. However a fatal error prevents me from handling the error using an error_handler. THAT is the problem. Best regards Christopher