David L. Nicol writes: > okay but we still have the hiding issue, in case we want it to What's the hiding issue? I must have missed that. > $one{two} is $one\two > $$one{two}{three} is $one\two\three > $$$one{two}{three}{four} is $one\two\three\four Your left hand side is, I think: $one->{two}{three}{four} in a very complicated fashion. I'm unsure this is what you meant. > with %one\two { > push @\three\four, 5,6; > } > is clear and invulnerable. Except that you often don't know the keys in advance, and so now your code turns into: with %one\$keytwo { push @\$keythree\$keyfour, 5, 6; } which is decided sub-clear. The precedent of "if you're doing a hash lookup, use {} around the key" is fairly well-ingrained in Perl. Nat
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was Re: implied pa... Markus Peter
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was Re: impli... Nathan Torkington
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was Re: i... David L. Nicol
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was R... Markus Peter
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was R... Nathan Torkington
- Re: PROTOPROPOSAL FOR NEW BACKSLASH w... David L. Nicol
- Re: PROTOPROPOSAL FOR NEW BACKSL... Michael Fowler
- Re: PROTOPROPOSAL FOR NEW BACKSL... Nathan Torkington
- Re: PROTOPROPOSAL FOR NEW BA... David L. Nicol
- Re: PROTOPROPOSAL FOR NE... Jonathan Scott Duff
- Re: PROTOPROPOSAL FOR NE... Damian Conway
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was R... Markus Peter
- Re: PROTOPROPOSAL FOR NEW BACKSLASH w... Bart Lateur
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was Re: i... Bart Lateur
- Re: PROTOPROPOSAL FOR NEW BACKSLASH was R... Randal L. Schwartz