Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45082
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.203 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;
        b=sfnsMEyhLqKvnxNLPQNc1xyvdojLKtE4tQlSQ5IDPvYh+1xMf/Fc6R8h9A6YfI0hWC
         86gvCJQFswCsWqDg4JdRWArfh/M+MdNI/cMhUXF5zrbwpq5c3bw6SH/G9YkOF6Neey+5
         5+5v38zfTz8YHTkShesC2CGKNZjBncJS8PG2k=
MIME-Version: 1.0
In-Reply-To: <C158D80C-1216-4CE6-AAF3-00B514170C8B@gmail.com>
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>
Date: Fri, 24 Jul 2009 09:32:29 -0700
Message-ID: <e2e02fe0907240932r3cf0e0dq3e83ddb326f4f58f@mail.gmail.com>
To: Matt Wilson <shadda@gmail.com>
Cc: Brian Moon <brian@moonspot.net>, internals@lists.php.net, 
	"Ben Scholzen 'DASPRiD'" <mail@dasprids.de>
Content-Type: multipart/alternative; boundary=000e0cd3eb827d5261046f762691
Subject: Re: [PHP-DEV] RFC: Replacing errors with Exceptions
From: chrisstocktonaz@gmail.com (Chris Stockton)

--000e0cd3eb827d5261046f762691
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Sorry for top post, on my android. I disagree that php has perl phobia, but
I agree that a alternative to errors needs to be made. Your example is nice
but might have some tricky implementation details if php continued to throw
errors when it didn't detect $!. I.E. fopen(...) or throw new
CustomException($!); when custom exception writes to a log file that also
writes to $! Perhaps for file not found, For example, does the first fopen
throw the error or supress it as the user likely wanted. However it becomes
a moot point if errors are still thrown.

On Jul 24, 2009 9:01 AM, "Matt Wilson" <shadda@gmail.com> 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?

On Jul 24, 2009, at 10:51 AM, Brian Moon wrote: > On 7/24/09 6:43 AM, Ben
Scholzen 'DASPRiD' wrot...

--000e0cd3eb827d5261046f762691--