t gets the localized value whenever $main::name is localized and the global value when not
No. When $name is executed, it gets the current value of $main::name. There's nothing conditional about it.
Any assignment to $main::name within the closure changes the global variable at whatever localization level it happens to be running in.
Again, it simply changes the variable $main::name. There's nothing conditional about it. Localisation just means a backed-up value will be assigned to the variable later.
Inside the foreach loop, the subroutine closes over whatever $name happens to be aliased to,
It captures the variable, whether it's an alias or not.
No matter where the subroutine runs, any assignment to $name within the closure changes the thing aliased, i.e. an element of @colors
If the captured variable is an alias, yes. That's what an alias is. It's got nothing to do with captures.
In the above quote from perlsyn it says both my and our are localized and doesn't make a distinction between aliasing and localizing. In your opinion is this a documentation bug? a perl bug? or neither?
They're independent.
I don't see anything wrong in perlsyn. Which statement is giving you pause?
* — In practice, my vars aren't actually created at declaration and destroyed at scope exit, but that's how they're specified to behave. In reality, it might actually simply be a localisation in this case.
In reply to Re^3: How do closures and variable scope (my,our,local) interact in perl?
by ikegami
in thread How do closures and variable scope (my,our,local) interact in perl?
by ELISHEVA
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |