Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100977
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain hotmail.co.uk designates 40.92.69.63 as permitted sender)
To: Stephen Reay <php-lists@koalephant.com>, Nikita Popov
	<nikita.ppv@gmail.com>
CC: Christopher Jones <christopher.jones@oracle.com>, PHP Internals
	<internals@lists.php.net>
Thread-Topic: [PHP-DEV] [RFC] Flexible Heredoc and Nowdoc Syntaxes
Thread-Index: AQHTRAW9Yd+8OMxyIE+nYJTWLiuSDaLyOqAAgACMG2eAAA6QgIAGKb+AgAAxaOU=
Date: Sat, 28 Oct 2017 11:17:37 +0000
Message-ID: <AM4PR0901MB12653AF45EBEF6A612430CA7F95B0@AM4PR0901MB1265.eurprd09.prod.outlook.com>
References: <AM4PR0901MB1265667C867226BD7B56E748F9480@AM4PR0901MB1265.eurprd09.prod.outlook.com>
 <0ac37ce7-62f4-7b1c-5b3d-2d2f45190f07@oracle.com>
 <AM4PR0901MB12657CCAAD6D6A825595E851F9470@AM4PR0901MB1265.eurprd09.prod.outlook.com>
 <CAF+90c8qkkSP8RzNFgYnfbxi4d7c9ya6zLTh7xan=2dDgBw8wQ@mail.gmail.com>,<4BD31E87-540B-42A3-9823-9FAFD21EEF0A@koalephant.com>
In-Reply-To: <4BD31E87-540B-42A3-9823-9FAFD21EEF0A@koalephant.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [cN6Zyun3qzvU2Qifr/YPB5k7GkmvfVjX]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1;VE1EUR02HT154;6:DywLbL5EYlLmLAXd4SM+nugDz00oaeSi6koCP27oLlSpwYYuS5I63vLG53qGqbwFRclThKxQAiH3/JAJqj2I7GMTP+q0WdQNEZltesrMHeZa9G/gUqkunzlkGWxPtbcEJbyEhQkwKh90z7uKVRa9aClMRwtIcdOCdJSHT+gJjTO59RdDJr9470fJ0s1USawpGNtL+4ML/lymUwmA0NE9KhppUsw4qJGc3ZvGuiQt6MbpP4YEbKBlPJgyt0dKmVV7ml8cs0HTM0FYczTl0D+BabXOz8k0cGjjBh/+SatMcshTCHkeVA/xA/Ob1hzXpoug9znINQye2Y1/7vI5AVADaA==;5:7kn2SYM4n7zMwfVoBAUHAMz4sDvOUHviKc23AHsLFvoQm9O/+mCfqRxZ+91CSuYZbm0+uGv6Mm7B7s3TX1mVaefE3C8RjlDWvmIE6iLNX97c/Tcu6VktPInwZ7ASNJSgCTZPUPK+/r71E1iwWiO9oA==;24:i4EwZ0IJ3tyVjX002XfgMjRWsymBz8aO06siCqk8K4fsHzI0vBAWHfvyqPycLKFTbWaJFdBn4sqs2lInmucke72YdbXcwhFV9iKqC6naeHE=;7:sOc3yfuBH7t4P9No883Z6mbkeSbqkXdqkJhx5Uj2hmMu8DFP6TKYUvRBaOBwnmxS1q9UF5lu8AgIdnVSjejUT8W0+xdDgcOc57RlfnGyvWOentF8cd9m1mNXsKZbr6kIdee+lKuo/aQ81h74msh2IV3I8dVH3+LnBEzxvTrFu3U3z9o/kw47kLW9VwRNcCNWiElwkj1favB0vAFxJFKKAj8bfGDvar1brtZA74B0/bU=
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-ms-office365-filtering-correlation-id: 31af021a-87e3-4b7e-6854-08d51df57f1a
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045);SRVR:VE1EUR02HT154;
x-ms-traffictypediagnostic: VE1EUR02HT154:
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031);SRVR:VE1EUR02HT154;BCL:0;PCL:0;RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095);SRVR:VE1EUR02HT154;
x-forefront-prvs: 04740D25F1
x-forefront-antispam-report: SFV:NSPM;SFS:(7070007)(98901004);DIR:OUT;SFP:1901;SCL:1;SRVR:VE1EUR02HT154;H:AM4PR0901MB1265.eurprd09.prod.outlook.com;FPR:;SPF:None;LANG:;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative;
	boundary="_000_AM4PR0901MB12653AF45EBEF6A612430CA7F95B0AM4PR0901MB1265_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 31af021a-87e3-4b7e-6854-08d51df57f1a
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2017 11:17:37.9110
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR02HT154
Subject: Re: [PHP-DEV] [RFC] Flexible Heredoc and Nowdoc Syntaxes
From: tpunt@hotmail.co.uk (Thomas Punt)

--_000_AM4PR0901MB12653AF45EBEF6A612430CA7F95B0AM4PR0901MB1265_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Stephen,

> I disagree. To me this change would simply mean that the literal exact wh=
ite-space string preceding the end marker is removed as a prefix from all l=
ines.
>
> So if you have an end marker intended by two tab characters, but all the =
=91content=92 lines of the heredoc are indented by 8 spaces, nothing is rem=
oved.

So let's say the ending marker is indented with [space][tab][space] and the=
 body is indented with [tab][space][tab], by your logic, a [space] and a [t=
ab] should be removed from the body's indentation? Or nothing at all?

The problem with such rules is that they bring more complication to the imp=
lementation when it comes down to the finer details. It is far better to si=
mply disallow such nonsense to begin with.

A nice benefit of this (choosing a stricter approach to begin with) is that=
, should we see advantages to bringing more leniency to the current semanti=
cs (such as enabling the mixture of tabs and spaces), then we can enable th=
is later without causing any new BC breaks. Whereas if we introduce a reall=
y loose-style syntax to begin with, then we cannot make it stricter later o=
n without introducing new BC breaks.

-Tom

--_000_AM4PR0901MB12653AF45EBEF6A612430CA7F95B0AM4PR0901MB1265_--