You will always be able to turn register_globals on.  Completely removing
that feature would make it impossible to ever run a lot of code written
for PHP.  Some will argue that this is a good thing, but ultimately it is
not for us to say.

When you turn register_globals on, $HTTP_* do not disappear.  What changes
is that the various Environment, Get, Post, Cookie, Server variables are
not automatically injected into the global symbol table.  You will have to
access them through either $HTTP_*_VARS['var_name'] or $_*['var_name'].
In the second case that would be $_ENV['var_name'], for example.

-Rasmus

On Sat, 2 Mar 2002, Scott Brown wrote:

> So - to confirm...
>
> If upgrading from a 4.0.x up to a 4.1.x version, putting register_globals =
> on in the /etc/php.ini will ensure that old code continues to run.
>
> But in the long term (ie, in some future php version), the $HTTP_* vars will
> no longer be supported.
>
>
> Is this correct?
>
>
>
> > -----Original Message-----
> > From: Andrey Hristov [mailto:[EMAIL PROTECTED]]
> > Sent: February 23, 2002 12:53 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [PHP] Re: php 4.1.1 vs 4.0.6
> >
> >
> > In 4.1.x series there are new vars (global scope)
> > $_GET,$_POST,$_COOKIE,$_FILES,$_SESSION
> > not available in 4.0.x versions. For old scripts could be
> > problem that register_globals is off in the 4.1.x tree(for new
> > installations, not upgrades). But this is for good.
> >
> > Regards,
> > Andrey Hristov
> >
>
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to