Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45083
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.198.233 cause and error)
Message-ID: <4A69EDF7.8000207@lerdorf.com>
Date: Fri, 24 Jul 2009 10:23:03 -0700
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Matt Wilson <shadda@gmail.com>
CC: Brian Moon <brian@moonspot.net>, 
 Ben Scholzen 'DASPRiD' <mail@dasprids.de>,
 internals@lists.php.net
References: <CD.98.39659.DC5B96A4@pb1.pair.com> <2dedb8a0907240640i118d220fte7ed4e0285aae024@mail.gmail.com> <CA.5A.39659.79AB96A4@pb1.pair.com> <4A69D866.9010108@moonspot.net> <C158D80C-1216-4CE6-AAF3-00B514170C8B@gmail.com>
In-Reply-To: <C158D80C-1216-4CE6-AAF3-00B514170C8B@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC: Replacing errors with Exceptions
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Matt Wilson wrote:
> I agree, however there are certain aspects of PHP's errors that leave a
> lot to be desired. For instance, a failed fopen or a failed socket will
> often result in an uncatchable warning from php. Sure, you can add a @
> to the line but that's slow and doesn't tell you anything about what
> happened.
> 
> I've been saying for years that PHP needs to get over its perl phobia
> and implement something like $!
> 
> fopen("file", "r") or throw new Exception("Error: ". $!);
> 
> Wouldn't that be nice?

I don't see the big difference between that and:

if(!fopen("file", "r")) throw new Exception();

and error_get_last() gives you the type, error message, line number, and
filename which you can access in your catch block.  Presumably you still
want to log these which you get for free so no need for the @.

-Rasmus