Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105248
To: Thomas Hruska <thruska@cubiclesoft.com>, Wes <netmo.php@gmail.com>,
 "G. P. B." <george.banyard@gmail.com>
Cc: PHP internals <internals@lists.php.net>
References: <CAFPFaMJEn=gjk5jAAxR2bF=4Mt3r0FJCm6mbOCReOmyybtAkkg@mail.gmail.com>
 <CAOv67gsiva80KEhw7D2N2qKCz0gZvza30EDL7SZoJRPFsGoROA@mail.gmail.com>
 <0ec42fa9-77d1-a203-8425-e72fdd5071f3@korulczyk.pl>
 <06473788-a34b-f041-36e6-31d19d8dda4c@cubiclesoft.com>
Message-ID: <59cafbfb-2bb0-468c-458f-74bcac780e0f@korulczyk.pl>
Date: Thu, 11 Apr 2019 18:51:28 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <06473788-a34b-f041-36e6-31d19d8dda4c@cubiclesoft.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] [VOTE] Deprecate PHP's short open tags
From: robert@korulczyk.pl (Robert Korulczyk)

> Turning it on permanently would also solve the problem 

Well, yes, although it creates "another way of doing the same thing". So far PHP was on a way to remove redundant tags. Permanently enabling of short
open tags looks like a move in the opposite direction.

Personally, I'm surprised by the controversy around this change. So far it was an obvious anti-pattern for me, and never seen anybody who was aware of
the consequences of using <? and still use <? instead <?php on purpose.

Regards,
Robert Korulczyk

W dniu 11.04.2019 o 17:36, Thomas Hruska pisze:
> On 4/11/2019 1:12 AM, Robert Korulczyk wrote:
>>> Sorry for the sarcasm, please don't consider this as a personal attack. The
>>> whole community (not just you) considers short open tags poison because not
>>> XML-compatible...
>>
>> This is rather removing another trap from the language. As long as short open tags exist and depend on INI directive, there will be bugs and source
>> code leaks after moving application to a different environment. Using <?php over <? is the only safe way to write PHP code, and now you need an
>> external tool to enforce this.
> 
> I wouldn't say it is the ONLY safe way.  Turning it on permanently would also solve the problem and there's also allowing '<?[whitespace character]'
> as a permanent always-on option.  (Native XML compatibility is a complaint, not a requirement of a language.  XML is also basically dead in my corner
> of the PHP universe, only ever cropping up on very rare and very confused occasions.)
> 
> It's going to be interesting to see how many people who rely on and *prefer* using short open tags in internal systems come out of the woodwork when
> PHP 7.4 and 8 drops.  Maybe I'm the only one who likes saving a few characters here and there and thinks code is more readable without the verbose tag.
> 
> The vote is on the knife's edge of passing/failing at the moment and could go a couple of unusual directions as already noted elsewhere. This is
> probably the most interesting RFC *vote* to happen in a long while.
>