Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106515
MIME-Version: 1.0
References: <CAJHtznw0eKbBNJo9TnDwZvvbMMFt5mCo=+SpKLw0zYzq9tKWZA@mail.gmail.com>
 <CAESVnVqz5d=CmLEEFZyJaTcKsg7H8m74xx5WUPb_gP42g6C5bA@mail.gmail.com> <CAJHtznzXey7pTt8utd1b8DEqNnRQ2SERq1uwqPJPcdSkrFGgTg@mail.gmail.com>
In-Reply-To: <CAJHtznzXey7pTt8utd1b8DEqNnRQ2SERq1uwqPJPcdSkrFGgTg@mail.gmail.com>
Date: Fri, 9 Aug 2019 17:50:42 -0500
Message-ID: <CAESVnVov7qnEA-HgJ09Y+OH0qAVPaVnCBcLHsmzo2PZh=0=u+Q@mail.gmail.com>
To: Zeev Suraski <zeev@php.net>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000a98918058fb7019c"
Subject: Re: [PHP-DEV] P++: FAQ
From: pollita@php.net (Sara Golemon)

--000000000000a98918058fb7019c
Content-Type: text/plain; charset="UTF-8"

On Fri, Aug 9, 2019 at 4:58 PM Zeev Suraski <zeev@php.net> wrote:

> As Bob pointed out I'm rusty, but I do think that we can solve the short
> tags issue in this way.  At the lexer level, if we see the <?p++?> tag, we
> set short tags to off for the scope of the file before moving forward.  But
> more importantly, this approach can allow us to implement different BC
> breaking strategies (and not just for language features, but also for
> built-in functions).
>
> That approach did occur to me to, but as I said in my earlier reply, I
don't think this actually addresses the goals set by the short tags removal
proposal *as I understand it*.  Maybe it does, but for example one could
still not start a file with "<?xml" as at this point the parser hasn't
encountered a "<?p++" tag yet, so it doesn't know if it should disable the
"<?" or not.

-Sara

--000000000000a98918058fb7019c--