Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45081
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.228 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=cc:message-id:from:to:in-reply-to:content-type
         :content-transfer-encoding:mime-version:subject:date:references
         :x-mailer;
        b=BwhzDVQQIzY2JoBKsb2v8xr5c774dMdVBM54jPnoBc0SQadmeJ9wdarJIflnhQ7SpV
         jZjiZRS1Y7dBVBqVJSH/+inw5PZk7WvoFFA+ZDI0KnV1nWKVl+D8YufVnHNgLRXV2Nmc
         XfXRIDDjPnV+5t7JLsG4QIUJLaEgUspkLixC8=
Cc: Ben Scholzen 'DASPRiD' <mail@dasprids.de>,
 internals@lists.php.net
Message-ID: <C158D80C-1216-4CE6-AAF3-00B514170C8B@gmail.com>
To: Brian Moon <brian@moonspot.net>
In-Reply-To: <4A69D866.9010108@moonspot.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 24 Jul 2009 11:00:09 -0500
References: <CD.98.39659.DC5B96A4@pb1.pair.com> <2dedb8a0907240640i118d220fte7ed4e0285aae024@mail.gmail.com> <CA.5A.39659.79AB96A4@pb1.pair.com> <4A69D866.9010108@moonspot.net>
Subject: Re: [PHP-DEV] RFC: Replacing errors with Exceptions
From: shadda@gmail.com (Matt Wilson)

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' wrote:
>> To you both, this is especially, for library code like Zend  
>> Framework.
>
> This tends to invalidate your entire argument IMO.  Changing the  
> core language because something is hard in an external framework  
> that only a small percentage of actual PHP developers use is not a a  
> good reason.
>
> On 7/24/09 6:40 AM, Kalle Sommer Nielsen wrote:
> > I'm a big -1, I don't see a big reason for wrapping all my code in a
> > try/catch block when im writing flat out procedural for example, PHP
> > isn't an OO-only language
>
> ++1 on that.
>
> Brian.
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>