Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118674
MIME-Version: 1.0
In-Reply-To: <eeabffad-4765-dd2c-73af-ea81d39dec12@gmail.com>
References: <CAJpLVh1tYVMSvfXjiuh5=V8Pki4QDFDB6vUQT=rE6k_boSdDNA@mail.gmail.com>
 <eeabffad-4765-dd2c-73af-ea81d39dec12@gmail.com>
Date: Tue, 20 Sep 2022 20:29:29 +0200
Message-ID: <CAJpLVh3QjZiW4N3p5GcgjuipYQeD+zd6yyx=z2YZmnan1F_78Q@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] One-line heredoc for better syntax highlightning
From: olleharstedt@gmail.com (=?UTF-8?Q?Olle_H=C3=A4rstedt?=)

2022-09-20 11:54 GMT+02:00, Rowan Tommins <rowan.collins@gmail.com>:
> On 19/09/2022 20:10, Olle H=C3=A4rstedt wrote:
>> More for users to learn? Don't you mean less, haha? This is an
>> arbitrary limitation of heredoc, that we can remove (it might not be
>> arbitrary from a yacc perspective, someone would have to explain that
>> if so).
>
>
> I don't think the rules for heredoc are arbitrary,  but they are quite
> specific: the end delimiter has to appear at the *start* of a line, so
> it can appear anywhere else in the text without prematurely ending the
> string:
>
> $foo =3D <<<FOO
> This is a normal heredoc
> this is not the end FOO
> this is:
> FOO;

Ya ok, this kills my idea. If heredoc was designed from start so that
the delimiter would not be allowed at all in the text, then it would
make sense. Weird that they did it like that, would be easy enough to
come up with a unique delimiter so that it would not cause a
problem... Obviously it can't be changed now without breaking
backwards compatibility.

Our product still supports PHP 7.2 sadly, but that's our own problem. :)

Thank you.

Olle