Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:104949
MIME-Version: 1.0
References: <CAFPFaML1KT2WMhUkZg4rZz3BDV68oPCCufx5+0c26Js--gXj_Q@mail.gmail.com>
 <000301d4e312$06a88190$13f984b0$@roze.lv> <CAFPFaMJ3Fg7B6X1UiyYOq18ypRZYRPuRDh76U=_hfnh9XWpzHw@mail.gmail.com>
In-Reply-To: <CAFPFaMJ3Fg7B6X1UiyYOq18ypRZYRPuRDh76U=_hfnh9XWpzHw@mail.gmail.com>
Date: Mon, 25 Mar 2019 21:42:14 +0200
Message-ID: <CAPhkiZzQyKUgtquvtpOUGcTfucoVRWBA8U2FV3bFdK+4va9K1g@mail.gmail.com>
To: "G. P. B." <george.banyard@gmail.com>
Cc: Reinis Rozitis <r@roze.lv>, Rasmus Schultz <rasmus@mindplay.dk>, 
	=?UTF-8?Q?Johannes_Schl=C3=BCter?= <johannes@schlueters.de>, 
	PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC] Deprecate PHP's short open tags
From: narf@devilix.net (Andrey Andreev)

Hi,

On Mon, Mar 25, 2019 at 8:02 PM G. P. B. <george.banyard@gmail.com> wrote:
>
> On Mon, 25 Mar 2019 at 16:38, Andrey Andreev <narf@devilix.net> wrote:
>>
>> OK, so why not flip it and make it always available instead? I'm aware
>> of the potential XML conflict, but I've personally never seen it, so
>> to me that looks like the lesser evil compared to a massive BC break.
>>
>> Cheers,
>> Andrey.
>
>
> Technically this is already the case, the default in the engine is to enable PHP's short open tags, however both INI config templates provided
> with PHP (php.ini-developement and php.ini-production) disable PHP's short open tags.
> So if PHP's short open tags are to be considered "full class" open tags this should be represented in the INI templates. But I won't be the
> one pushing for this change.
>

We're talking about removal of the INI setting ... Aside of saying you
wouldn't be personally pushing for what I suggested, I don't get the
point of what you wrote.

Cheers,
Andrey.