Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:83272
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.49 as permitted sender)
MIME-Version: 1.0
Reply-To: marcio3w@gmail.com
Date: Fri, 20 Feb 2015 04:29:18 -0300
Message-ID: <CAOsHV+vOuvGxAz6EEjhwCL3fGN2YiNB1OfaJTfnFaKNB6-0SKg@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1133ad5ce46dde050f800324
Subject: [RFC][DISCUSSION] Context Sensitive lexer
From: marcio.web2@gmail.com (Marcio Almada)

--001a1133ad5ce46dde050f800324
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi internals,

I'd like to put the "Context Sensitive Lexer" RFC into discussion phase:

RFC: https://wiki.php.net/rfc/context_sensitive_lexer
TL;DR commit: https://github.com/marcioAlmada/php-src/commit/c01014f9
PR: https://github.com/php/php-src/pull/1054

PHP currently has ~64 globally reserved words. Not infrequently, these
reserved words end up clashing with legit alternatives to userland API
declarations. This RFC proposes minimal changes to have a context sensitive
lexer with support for semi-reserved words on PHP7 without causing
maintenance issues.

This could be especially useful to:

   - Reduce the surface of BC breaks whenever new keywords are introduced
   - Avoid restricting userland APIs. Dispensing the need for hacks like
   unecessary magic method calls or prefixed identifiers.

The patch is 98% finished, the entire test suite is passing. I'm still
adding more tests to it but the hard part is done. So it's time to discuss!
Sincerely,
M=C3=A1rcio Almada

--001a1133ad5ce46dde050f800324--