Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118677
Message-ID: <1d4ffc2a-b636-2c4b-aaf2-4c448312bcaf@gmail.com>
Date: Tue, 20 Sep 2022 20:34:47 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Content-Language: en-GB
To: internals@lists.php.net
References: <CAJpLVh1tYVMSvfXjiuh5=V8Pki4QDFDB6vUQT=rE6k_boSdDNA@mail.gmail.com>
 <eeabffad-4765-dd2c-73af-ea81d39dec12@gmail.com>
 <CAJpLVh3QjZiW4N3p5GcgjuipYQeD+zd6yyx=z2YZmnan1F_78Q@mail.gmail.com>
In-Reply-To: <CAJpLVh3QjZiW4N3p5GcgjuipYQeD+zd6yyx=z2YZmnan1F_78Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] One-line heredoc for better syntax highlightning
From: rowan.collins@gmail.com (Rowan Tommins)

On 20/09/2022 19:29, Olle Härstedt wrote:
> 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.


For what it's worth, the "they" in question are the authors of the early 
Unix shells in the 1970s - from a quick search, it seems like the Bourne 
shell was the first to implement "here document" syntax, sometime around 
1979. As the name suggests, they were not for defining strings, but for 
entering entire text files embedded in a script or interactive shell 
session.

In that context, the original format is actually elegantly minimal: 
content is read one line at a time; if it exactly matches the delimiter, 
stop; else, add the line to the file buffer. No actual parsing is required.

Regards,

-- 
Rowan Tommins
[IMSoP]