in reply to Best practices with globals and subroutine arguments
Your problem isn't that using globals is dangerous. Your problem is that the responsibility for many separate things is all over your program.
Extract separate behaviors and encapsulate separate responsibilities and you'll discover that the need for passing around lots of arguments and referencing and dereferencing lots of values will go away.
|
|---|