Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:77153
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <F005B7B2-9407-4387-826C-E0FFAFE7C8B7@ajf.me>
References: <CAF+90c_V0S6KhCLvkRZEcaQQ-Qv_oNaV9EJ_faOo9ZnVRLXQ0g@mail.gmail.com>
	<3619E7A6-6D76-498D-9082-855DAE937C1E@ajf.me>
	<F005B7B2-9407-4387-826C-E0FFAFE7C8B7@ajf.me>
Date: Thu, 11 Sep 2014 15:24:21 -0700
Message-ID: <CAKOpQSxCAY98GmzBFSz76chk+HXsS3gbE1KAJfGAAxuYR9topw@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e0122976254185a0502d1a19b
Subject: Re: [PHP-DEV] Remove alternative PHP tags
From: kris.craig@gmail.com (Kris Craig)

--089e0122976254185a0502d1a19b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Sep 9, 2014 at 6:32 PM, Andrea Faulds <ajf@ajf.me> wrote:

>
> On 10 Sep 2014, at 01:21, Andrea Faulds <ajf@ajf.me> wrote:
>
> > Isn=E2=80=99t this a bit of a needless BC break? Not very nice on peopl=
e with
> such codebases. It=E2=80=99s also worth pointing out that people might be=
 using
> these to get around the XML <? issue (granted, you can disable short tags=
).
> >
> > I=E2=80=99d vote for this if you wrote a convertor script to help peopl=
e
> migrate. Otherwise I think we=E2=80=99re just being unfair on people who =
used these
> tags.
> >
> > Actually, I=E2=80=99d like to see a Python 2to3-esque tool in general f=
or PHP 7.
> The easier we make the migration, the more likely people will do it.
>
> Some further thoughts after discussing with Tyrael (Ferenc) on IRC.
>
> I initially thought that I=E2=80=99m not really against removing them rea=
lly, but
> I think we should have a script to convert them first. Because someone,
> somewhere, is gonna need it.
>
> But then I=E2=80=99ve thought more about it. I=E2=80=99m usually OK with =
certain BC
> breaks, I just don=E2=80=99t like this specific one. It doesn=E2=80=99t a=
ffect me, but,
> well, I don=E2=80=99t see the point. It doesn=E2=80=99t really help langu=
age consistency or
> anything, (OK, sure, only two sets of delimeters now, but it=E2=80=99s no=
t a big
> deal like some other things are), and you=E2=80=99ll force people to upda=
te every
> file in their codebase if they=E2=80=99re affected, assuming people who u=
se
> alternative tags use them everywhere. There=E2=80=99s also a security iss=
ue here.
> If someone uses PHP 7 with a codebase that has these alternative tags, yo=
ur
> code is now visible to users instead of the output, which might include
> configuration details like database passwords or password hash salts. It=
=E2=80=99s
> also possible that people won=E2=80=99t notice this is happening if they =
only used
> these alternative tags in a few obscure places.
>
> I wonder if, really, we might be better off keeping them around and just
> outputting E_DEPRECATED. If we do get rid of them in 7, we should have 5.=
7
> deprecate them.
> --
> Andrea Faulds
> http://ajf.me/
>
>
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>
I think Andrea raises a valid point about BC.  I agree that those old tags
should go, but I'd suggest we target that removal for PHP 7 and just add a
deprecated flag on 5.x.

--Kris

--089e0122976254185a0502d1a19b--