Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80633
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.212.180 cause and error)
MIME-Version: 1.0
In-Reply-To: <54B8E333.1010501@lsces.co.uk>
References: <8DCD1B72-C81D-499E-B455-E4A042CD76E6@ajf.me>
	<000301d02fd3$456ab390$d0401ab0$@tutteli.ch>
	<CAOsHV+thK_3CbY8BQn+M5-jS8b54zqwmEKERKdXfSE1fVoQJSQ@mail.gmail.com>
	<89065BA9-7D1E-43DE-881F-CF15C38AA27F@ajf.me>
	<CAL0xaBEM6AvcQMFTaWkyGt2uvQnx+nS+oJzi+xkr=WDYRmX+Zw@mail.gmail.com>
	<op.xsifxpka7q1gix@nikita-hp.seopult.ru>
	<54B8E333.1010501@lsces.co.uk>
Date: Fri, 16 Jan 2015 12:05:29 +0100
Message-ID: <CAEPJdukmkSgRS8pORa=p8Ug8gY8Gz1bz=QxX+ah3c+WaG9_s6A@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=047d7b5d997f585422050cc2f385
Subject: Re: [PHP-DEV] [RFC] Scalar Type Hints v0.2
From: kontakt@beberlei.de (Benjamin Eberlei)

--047d7b5d997f585422050cc2f385
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 16, 2015 at 11:08 AM, Lester Caine <lester@lsces.co.uk> wrote:

> On 15/01/15 15:28, Niktia Nefedov wrote:
> >> Consider what a mess was register_globals and problems it had, but at
> >> least
> >> it was a global setting. Declare will work on per file basis, and it
> will
> >> end up even more of a mess.
> >>
> >> I think PHP development community learned that lesson and that's why you
> >> get pushback, and not only from internals, but also from the userland.
> Me
> >> including.
> >
> > What does it have with register_globals in common? Why would it be a
> mess?
>
> Removing 'register_globals' breaks code for users who have no idea that
> their sites are even using it. deprecating on one version - which one is
> told to switch off the warnings for - just means that when the hosting
> skips a version the site simply stops working. That is why 5.2 is still
> around and why hosting companies have problems ... and I still have code
> which relies on 'register_globals' today because those sites are simply
> working. There is simply no time to 'fix' them :(
>
> At the end of the day the whole of the legacy codebase either has to be
> brought forward, or PHP5 will be hanging around for some of the same
> reasons PHP4 did. Bringing in more areas where differences between code
> bases can diverge again over time is creating the same black holes in
> the future.
>

You keep bringing this up, but there is a workaround to manually "enable"
register globals again if you need to have it for migration. It should just
work (TM) (haven't actually used it)

foreach ($_REQUEST as $k => $v) { $GLOBALS[$k] = $v; }

Not sure why we have to discuss this over and over again on this list.

>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=contact
> L.S.Caine Electronic Services - http://lsces.co.uk
> EnquirySolve - http://enquirysolve.com/
> Model Engineers Digital Workshop - http://medw.co.uk
> Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--047d7b5d997f585422050cc2f385--