I ... see the current language in perlvar as a "bug in the documentation."
I must disagree that it's a documentation bug. A symbol like $1 is just a name slapped on underlying data. It's a convenience. The underlying data may have special properties, like immutability in the case of the $1 capture group variable. There are many special and "magical" variables in Perl. If the previously defined name of a variable is "aliased away" to another variable, the special properties of the original variable don't go with it. That's a feature of aliasing and must be understood as such. To be consistent, the documentation would have to say, for every Perl variable with any special property, that the special property will not transfer to another variable if the variable's original symbolic name is aliased to the other variable.
I must admit that the extremely idiosyncratic use in the OP of $1 as a for-loop variable had me going for a bit. I think it's syntactically correct, however, and likewise the docs, and any problem lies with the OPer's understanding and use of the language.
Give a man a fish: <%-(-(-(-<
In reply to Re^6: Getting an unknown error
by AnomalousMonk
in thread Getting an unknown error
by andybshaker
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |