Re: Using $HTTP_SESSION_VARS with register_globals On
| From: | Zeev Suraski | Date: | Sat, 23 Jun 2001 13:36:36 +0000 |
| Subject: | Re: Using $HTTP_SESSION_VARS with register_globals On | ||
| References: | 1 2 3 4 5 6 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-57758@lists.php.net to get a copy of this message | ||
When releasing 4.0.6 I noticed this change (I didn't take active part in the discussion). Can someone bring me up to speed as to:
(a) Why was it impossible to write portable code with register_globals being off
(b) Why does it make sense to have $HTTP_SESSION_GLOBALS behave in an inconsistently with the way the other $HTTP_*_VARS[] behave?
With this change we went one step away from consistency, at least as long as the other $HTTP_*_VARS[] behave as they do today. It may be a good step, but if it is, it should be followed by other steps to keep consistency...
Zeev
At 14:54 22/5/2001, Andrei Zmievski wrote:
On Tue, 22 May 2001, Andi Gutmans wrote:-- Zeev Suraski <zeev@zend.com> CTO & co-founder, Zend Technologies Ltd. http://www.zend.com/As I mentioned in my other message, $HTTP_SESSION_VARS value and the global value used to be references, but after some people complained about this fact on the list, it was changed.. I wouldn't mind reinstating it, but if we do, let's do it once and for all with very good reasons to avoid another such occurrence.Making them references is the right thing IMO. I think we should also write in the manual that people should use $HTTP_SESSION_VARS[]. (I haven't checked if this is written or not so it might be already). Ok, we'll make them references then. I hope someone documents it, though, because I don't have time right now. -Andrei * Software never has bugs. It just develops random features. * -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net For additional commands, e-mail: php-dev-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net