Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33400
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.189 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=am+ldEHICjmWD6K8Hq4S+kvudyyBa3xMpCIKuHWuuFCNPArFTVkPRoSngiBRJz/q61hPNIqZGQ0Vfz5ER4RKUdS+dNSL5xxeW2B14/irq78J4vAYueWs5/0+glEICxw4XLfu3ONw0pAvX7PVlA/EWx844XaG4mvePvzFmXAM05k=
Message-ID: <ab5568160711230949s53bd888n4f485d25e9e9012a@mail.gmail.com>
Date: Fri, 23 Nov 2007 12:49:42 -0500
To: "Ken Stanley" <dohpaz@gmail.com>
Cc: "Evert | Rooftop" <evert@rooftopsolutions.nl>, internals@lists.php.net
In-Reply-To: <c70e053d0711222132n3a7e403fn8041c5460ea5ed65@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c70e053d0711211912m1bb79c18uf6e85ba7cd736636@mail.gmail.com>
	 <474511C7.4030501@rooftopsolutions.nl>
	 <c70e053d0711222132n3a7e403fn8041c5460ea5ed65@mail.gmail.com>
Subject: Re: [PHP-DEV] Quick question before submitting a feature request...
From: parasane@gmail.com ("Daniel Brown")

    Ken,

    This same issue was referred to back in 2004 on the php.net site.
I just looked it up and the post can be found by ptah@se.linux.org
from 9 September, 2004, on this page:
        http://us.php.net/errorfunc


On Nov 23, 2007 12:32 AM, Ken Stanley <dohpaz@gmail.com> wrote:
> I completely agree with what you and Alexy suggest. I've since refactored my
> code accordingly so that an exception would not be thrown while inside of an
> exception. But, that does not answer my original question. I asked about
> submitting a feature request that would simply provide more information in
> the unfortunate event that anybody's code inadvertantly throws an exception
> while in an exception, and whether or not it would be advantageous to do so,
> or if work was already being done on this very issue.
>
> The current error provides no information at all (e.g., no file name or line
> number of the offending exception), which in some cases makes it nearly
> impossible to debug. My apologies if I was not clear enough in my first
> e-mail. :)
>
> On Nov 22, 2007 12:21 AM, Evert | Rooftop <evert@rooftopsolutions.nl> wrote:
> >
> > Perfect code should catch every exception. If your code is at a point
> > where exceptions can be thrown, you should be using catch to actually
> > catch the exception and handle the exception appropriately.
> >
> > set_exception_handler should in fact only be used to spot a bug in your
> > code.. A bug being in this case, not catching an expected exception. Its
> > the last fallback.. If you really need complex code tied to your
> > exception handler, then use a try..catch block there too..
> >
> > Evert
>
> >
>
>
>
> --
> It looked like something resembling white marble, which was
> probably what it was: something resembling white marble.
>                -- Douglas Adams, "The Hitchhikers Guide to the Galaxy"
>



-- 
Daniel P. Brown
[office] (570-) 587-7080 Ext. 272
[mobile] (570-) 766-8107

If at first you don't succeed, stick to what you know best so that you
can make enough money to pay someone else to do it for you.