I keep forgetting to look into whether alternative methods of listing variables
And you continue to ignore the fact that we are advocating a programming style where you never have to do massive lists of variables, because all the active variables are local to the current subroutine. Any longer-lived values live in a very very few globals, or in objects that can operate on their own contents.
I don't know how anyone could say that the addition of a reset feature that's more flexible and safer than Perl's not-yet-deprecated reset function is a bad addition,
We're not saying that such an addition would be bad. We're saying that such an addition has already been made, and its name is my. Variables so declared are "reset" at the end of the block, with no additional code needed! Magic!
We see you driving around an old jalopy that's leaking oil and basically being a mainenance nightmare. Doesn't matter whether you wrote it, or if you just inherited it. We are suggesting that you fix the car; you keep on wanting to build a bigger and better tow truck.
As before, I wish you luck. Especially because, with this programming style and development mindset, you are going to need it.
In reply to Re^7: VarStructor 1.0
by tkil
in thread VarStructor 1.0
by Wassercrats
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |