Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49570
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain immomigsa.ch from 94.103.100.39 cause and error)
Date: Sun, 5 Sep 2010 14:30:35 +0200
To: internals@lists.php.net
Message-ID: <20100905123035.GA3759@croustillant.local>
References: <AANLkTikyZKnSL4=OS4-qn2G8c4QAYQ1oSe=bWa_Uo_Q-@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <AANLkTikyZKnSL4=OS4-qn2G8c4QAYQ1oSe=bWa_Uo_Q-@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [PHP-DEV] "or throw new" syntax
From: colder@php.net (Etienne Kneuss)

On Sep 05 14:19:16, Kalle Sommer Nielsen wrote:
> Hi
> 
> Is there any reason for we don't support expressions like:
> 
> test() or throw new Exception('test() failed');
> 
> 
> If no, is there any argument against supporting such a syntax in trunk?

Technically, it should be quite easy to have that available, but it
might become tricky to handle cases like: foo(throw exception()); or
even "throw throw throw new Foo;" ? :)

Also, I consider "or die" patterns to be a bad idea, extending it for
exceptions might make it a tad bit better, but I still find that bad
because of i.e. non trivial precedence rules:

include("foo") or throw new Exception("ads");

it will neither include "foo" nor throw any exception.

> 
> -- 
> regards,
> 
> Kalle Sommer Nielsen
> kalle@php.net
> 
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
> 

-- 
Etienne Kneuss
http://www.colder.ch