Hypothetical situation: I\'m running a complex site in php, and i use a lot of global variables.
i could store the variables in an existing global scope, say $
Both are pretty bad. I would suggest using a singleton, or static classes.
As for memory uses, there would be no noticable difference.
Your global variables are already accessible in $GLOBALS['foo'], $GLOBALS['bar']
etc. This is a clearer indication inside function scope that they come from the global scope than using the global
keyword. Should not affect performance in any meaningful way.
Many will tell you that best practice is to avoid global variables in the first place and instead pass variables through function calls and object constructors.