Re: backwards compat for newly developed scripts ($_GET / $HTTP_GET_VARS)

From: Date: Wed, 02 Oct 2002 12:46:24 +0000
Subject: Re: backwards compat for newly developed scripts ($_GET / $HTTP_GET_VARS)
References: 1 2 3  Groups: php.general 
Request: Send a blank email to php-general+get-118588@lists.php.net to get a copy of this message
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 yeah, at the top of each function....where you would normally put "global $HTTP_GET_VARS;" The created $_GET is not a superglobal so its scope is only in the function its defined in or if you define it in the global namespace you'd have to "global $_GET;" inside of your function & I'm sure that'll conflict with the superglobals on newer versions. On Wednesday 02 October 2002 12:13 am, Sascha Cunz wrote: > At the top of each _function_? Urgs. Sounds like a hell of a lot of work. > Would be enough at the beginning of the script - or even better, creating a > dummy include for that or it might even be posibile to run it via an > .htaccess (how is this option named php_prepend or such?). > > ... > > If they can't update the PHP Version they should update the ISP :-) Well, > 4.0.6 might be a "famous" release (as you can find this very often), but > it's about 1 year old now... If ISPs don't updated, they make their own > machines vulnerable - the only conclusion (to make them learn their lesson) > can be, that customers keep on running away, ain't it? Thats if they notice the one or two clients that leave over this issue. :| - -- ~Paul Nicholson Design Specialist @ WebPower Design "The web....the way you want it!" paul@webpowerdesign.net "It said uses Windows 98 or better, so I loaded Linux!" Registered Linux User #183202 using Register Linux System # 81891 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9muqkDyXNIUN3+UQRAiHUAJ4mxVd+makwIpmvsgIYauKCPl+mhwCeMrFA z4cX5Z3+ib/hirVLc5cSHbA= =Se8t -----END PGP SIGNATURE-----

« previous php.general (#118588) next »