Now we run directly into the tree called "Reality" in our idealic car.jshpro2 wrote:If you really needed your 'config' vars to be editable at runtime, it's a more solid solution to use a master array for configs, as opposed to variable variables (which can lead to issues)
The game uses *hundreds* of config variables across 30,000 lines of code. It is beyond unrealistic to change them all (and only those variables, not the other similarly named, similarly placed, and similarly scoped variables around them) to be $configure['something'].
While it is somewhat possible that the config variables don't get changed during the course of many files (favoring your define idea), it is not at all possible to change them all to a new prefixing scheme.
Idealism, meet the cold harsh reality of far too much legacy code.
Further, if I'm going that far down the road of idyllic lane, I'm going to a registry class, ya know?
update:
Abstract fud must end. Cite an example. My code uses variable variables, without issue, and both of the alternatives have stated, agreed upon "issues". Please, be specific, or don't scare off people of a useful tool.jshpro2 wrote:as opposed to variable variables (which can lead to issues)