Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105232
To: 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>
Message-ID: <0ec42fa9-77d1-a203-8425-e72fdd5071f3@korulczyk.pl>
Date: Thu, 11 Apr 2019 10:12:09 +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: <CAOv67gsiva80KEhw7D2N2qKCz0gZvza30EDL7SZoJRPFsGoROA@mail.gmail.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)

> 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.


Regards,
Robert Korulczyk


W dniu 10.04.2019 o 23:49, Wes pisze:
> Finally!!! everybody will be able to parse my xml files with embedded
> php!!!!1!1 if I ever wrote one!!!
> 
> 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... while they use stuff like twig, which is also not
> XML-compatible.
> 
> This is just beyond my understanding.
> 
> But sure, let's keep vilifying this kind stuff and pretend they are the
> root cause of PHP's bad rep.
> 
> Sorry again for the negativity.
>