Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106513
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=turbo-smtp; d=php.net;
	h=Received:Received:X-TurboSMTP-Tracking:X-Gm-Message-State:X-Google-Smtp-Source:X-Received:MIME-Version:References:In-Reply-To:From:Date:X-Gmail-Original-Message-Id:Message-ID:Subject:To:Cc:Content-Type;
	b=hkHGgqGZ9g6pNEJDiJ3kpNqqmJHVJ6jGojZ+qLNcivmQ2kziipW+au5NzHwJhC
	ixl02AKCz23xV6eQUWirY3Yq9Y/eik5GSBCbRbkt0coNnv/vQqtHEBkPAz0fttjg
	TRL4ukq8YSISfAlqVqnQkqwodc1eDxw6tTrkO7EMGq6r8=;
MIME-Version: 1.0
References: <CAJHtznw0eKbBNJo9TnDwZvvbMMFt5mCo=+SpKLw0zYzq9tKWZA@mail.gmail.com> <CAESVnVqz5d=CmLEEFZyJaTcKsg7H8m74xx5WUPb_gP42g6C5bA@mail.gmail.com>
In-Reply-To: <CAESVnVqz5d=CmLEEFZyJaTcKsg7H8m74xx5WUPb_gP42g6C5bA@mail.gmail.com>
Date: Sat, 10 Aug 2019 00:58:13 +0300
Message-ID: <CAJHtznzXey7pTt8utd1b8DEqNnRQ2SERq1uwqPJPcdSkrFGgTg@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000fb592d058fb6457f"
Subject: Re: [PHP-DEV] P++: FAQ
From: zeev@php.net (Zeev Suraski)

--000000000000fb592d058fb6457f
Content-Type: text/plain; charset="UTF-8"

On Sat, Aug 10, 2019 at 12:03 AM Sara Golemon <pollita@php.net> wrote:

> On Fri, Aug 9, 2019 at 2:54 PM Zeev Suraski <zeev@php.net> wrote:
>
> > It's available here:  https://wiki.php.net/pplusplus/faq
> >
> >
> It's possible I missed something while on holiday. There are certainly a
> lot of messages to page through.  I dig the idea of resolving this
> tug-of-war between progress and BC, but I'm not 100% clear on what the
> final goals are.  I understand that we're talking about more aggressively
> breaking BC in this new mode while preserving BC in "normal" PHP files, but
> I think it would help the conversation if we enumerated specific aims.
>
> Some guesses on what we're talking about:
> [snip]
> Am I *completely* off base?
>

I don't think you are.  In addition to these and those brought up by Mark -
other things could be making the new dialect stricter across the board -
including operators, array indices;  Requiring variable declarations;
Potentially changing some conversion rules (for explicit conversions), and
potentially changing some operator behavior (not just in terms of
strictness).

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).

Zeev

--000000000000fb592d058fb6457f--