Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66213
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <512BA9A6.6030006@oracle.com>
References: <CAF+90c8o=0u3deM6LA6TW9GjDeNrZA_16TAPBmHJQ7mN_P4v+A@mail.gmail.com>
	<512BA9A6.6030006@oracle.com>
Date: Mon, 25 Feb 2013 19:41:59 +0100
Message-ID: <CAEZPtU6EvFCdmi8ntfK5iYV6V984WPeALgrC-6qekJ2d7rfMjw@mail.gmail.com>
To: Christopher Jones <christopher.jones@oracle.com>
Cc: PHP internals <internals@lists.php.net>, Sara Golemon <pollita@php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Allow (...)->foo() expressions not only for `new`
From: pierre.php@gmail.com (Pierre Joye)

hi,

On Mon, Feb 25, 2013 at 7:12 PM, Christopher Jones
<christopher.jones@oracle.com> wrote:

> I think a brief RFC would be good to clarify and give some more examples of
> what "any expression" is.  Seeing more examples would help people
> evaluate the impact and see the use cases. It would also help the doc
> process.
>
> (For me, it's changes like Sara's trailing comma proposal that are too
> small to have needed an RFC)


I think there is no small enough changes in the syntax or in the
engine that would not justify a RFC. There is always (or almost
always) edge cases being caught up while writing or rewieving a RFC.


-- 
Pierre

@pierrejoye