Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45078
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.210 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=wB6VghnuTC4MBPoZYx+AJNEsWUBvl2pPaUXz2e6VxExPnI1BJbxebsK0a1vZVUaEVu
         XZr7GFbHGIOatugDVV1hmvZ4eWWQOeVWjgBRF5MZ4wmRrsKl+9FQa83Nx1jdMrKJEhP5
         14QZPxTBMYU6JOm3OkiuMhBGxultNcGzEYb5I=
MIME-Version: 1.0
In-Reply-To: <7f3ed2c30907240729i16a07871q2eb165c36f27752c@mail.gmail.com>
References: <CD.98.39659.DC5B96A4@pb1.pair.com>
	 <2dedb8a0907240640i118d220fte7ed4e0285aae024@mail.gmail.com>
	 <CA.5A.39659.79AB96A4@pb1.pair.com>
	 <7f3ed2c30907240729i16a07871q2eb165c36f27752c@mail.gmail.com>
Date: Fri, 24 Jul 2009 18:35:09 +0400
Message-ID: <cd5680a20907240735h31019559j8038349449a68c0b@mail.gmail.com>
To: Hannes Magnusson <hannes.magnusson@gmail.com>
Cc: "Ben Scholzen 'DASPRiD'" <mail@dasprids.de>, internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Replacing errors with Exceptions
From: indeyets@gmail.com (Alexey Zakhlestin)

On Fri, Jul 24, 2009 at 6:29 PM, Hannes
Magnusson<hannes.magnusson@gmail.com> wrote:
> On Fri, Jul 24, 2009 at 15:43, Ben Scholzen 'DASPRiD'<mail@dasprids.de> wrote:
>> To you both, this is especially, for library code like Zend Framework.
>> The library cannot expect the user to have the error handle set, so it
>> would have to replace the error handler before every line which it wants
>> to try {} and reset it after the catch. This is not really a clean
>> solution, at it can occur pretty often.
>
> Why do you have to replace it?

because in case of a library, there is a "third-party" called "user".
User might have his own opinion on error-handlers. And then, there's
even worse case, when there are 2 or three libraries mixed in the
single project

> You RFC says you want to throw exceptions for all E_WARNINGs - thats
> exactly the same as *not* restoring it.
> Just register errorhandler for E_WARNING and thats it.
>
> The libxml extension already has functionality to suppress XML errors,
> so your simplexml_load_file() example is bogus.
> Better example is fopen() on network failures, but even then I don't
> understand the problem.
>
>
> -Hannes
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>



-- 
Alexey Zakhlestin
http://www.milkfarmsoft.com/
Sent from St Petersburg, Russian Federation