What if you were maintaining someone else's 3000 line script that used all globals and you wanted to serve the script over and over as a web app? You might find they need to be reset before each iteration of the script. How would you would handle resetting variables without VarStructor? Would you "walk the symbol table" and rebuild my solution even if mine runs faster, is easier, and works for the script? Would you spend countless hours rewriting the code? If it were your script and you were a "good" programmer and only used the occasional global, you could find yourself in the same situation.
Sometimes a global is the best choice of variable. You could use the extremely flexible variable listing functionality of VarStructor to identify the variables and hard code a reset ($var = ''), or you could use the equally flexible reset feature (which is more flexible and safer than Perl's reset function) for an easier but slightly slower-running solution.
In reply to Re: VarStructor 1.0
by Wassercrats
in thread VarStructor 1.0
by Wassercrats
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |