Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85007
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <55068E88.3090401@lsces.co.uk>
References: <CANUQDCgY2-rS7B9WynvEqRXMKzC-y+fgTYvfUN8gsUqNPYjnsw@mail.gmail.com>
	<CADyq6s+yq1inZ6twiAjxXY_3DtQqc=nA0arW24KEXFethq2qAg@mail.gmail.com>
	<55068E88.3090401@lsces.co.uk>
Date: Mon, 16 Mar 2015 08:59:19 +0000
Message-ID: <CAPwsocHStLgXdEbrLJG_9oJHCYghnmmb5nvC_jYA1KOn5_LfOw@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=bcaec52be9bfc5a86c051164100a
Subject: Re: [PHP-DEV] [RFC][VOTE] In Operator
From: leight@gmail.com (Leigh)

--bcaec52be9bfc5a86c051164100a
Content-Type: text/plain; charset=UTF-8

On 16 March 2015 at 08:04, Lester Caine <lester@lsces.co.uk> wrote:
>
> Some of this Syntactic sugar would in the past have been developed in
> PEAR, but the support for 'userland' solutions via that path seems to
> have lost favour, with even the suggestion that PEAR should be dropped?
> Perhaps if PEAR contained examples of good practice in these areas it
> would help. I'd even perhaps go as far as suggesting that some of the
> more exotic developments in core would benefit from up to date demo's of
> their use in PEAR?
>

And how do you propose the lexer/parser is extended in this manner?

--bcaec52be9bfc5a86c051164100a--