This simply will not change.  It is a characteristic of the language.  Perhaps you shouldn't be using 20 global variables?

See http://marc.theaimsgroup.com/?l=php-general&m=97984136422910&w=2

I agree with Rasmus (and I really like his story :-), but to help you shoot yourself in the foot:

Declare and use your globals like this:
$g->id = 1000;
$g->username = "Marc";
// etc. until you have 20 of them

function fn() {
    global $g;
    $g->username = "Rasmus";
    }
with the added benefit of auto-global for any new global var you add in a later stage of the project.

This looks very similar to using $GLOBALS["username"] inside your function, which is what I use if I desperately _need_ a global.

Cheerio, Marc.

Changing this would break waaay to much, and it's against the nature of PHP.
i think it's a bad idea to change this.

Derick

#1 don't use globals. period. we are *not* going to change the language to support bad design techniques

#2 you can get all global symbols by doing

foreach($GLOBALS as $key => $value) global $$key;

bogusified

Thanks for the suggestions, I think I will stick all my globals in a structure since this won't be changed.

I agree that globals are not good in an object oriented language, but I still disagree about this - I would venture to guess that PHP is used mostly for small scale scripting, and the needs of the many - smallness and simplicity - outweigh the needs of the few poor saps who are trying to write an OS with it.

Interestingly, the one-line solution for accessing globals seems to be causing PHP.exe to hang.
I have narrowed it down to the following code which makes php die under WinXP (at least it does here)


<?
	session_start();
	session_register("Ses");
	$Ses->UserAdvanced = true;
	function test()
	{
		foreach($GLOBALS as $key => $value) global $$key;	// get access to all globals
	}
	test();
?>

ok, try this then:

foreach($GLOBALS as $key => $value) if($key != "GLOBALS") global $$key;

That new method makes the problem less common but it still occurs.  Shouldn't PHP produce an error rather than hang anyway?  I have been working on this for 3 hours and I still have the PHP lockups, but it's very unpredictable and I can't seem to find a concise sample to repro.  It's very strange because it doesn't appear to hang on that line, but rather on very innocent stuff long afterwards.  I'm giving up on it for now, but this may be something you guys want to look into further.