Note: Invalidity follows.
The topic title pretty much sums it up. This doesn't only affect variables explicitly declared global outside any scope, but also affects class declarations.
Reasons include:
- This is a confusing and obscure source of bugs.
- Sometimes declaring variables first isn't the best way of ordering code.
- Consistency: Super-global classes make classes similar to functions in that they are available everywhere, except for the requirement that classes be declared first whereas functions can be declared anywhere.
- If inter-dependent class declarations (class x extends y) are in separate files, including the files in the wrong order can break the script -- and this should never be the case. (See: Be able to define a base class after the child class)
I realize it may not be simple to implement, but I would certainly be willing to sacrifice a few milliseconds of load-time performance (once, when ahk starts) to do an extra loop through the script to identify variables that need to be treated as super-global. Especially if it means that we gain substantial consistency and remove obscure behavior.
Login
Register
FAQ
Search
