|
|
|
| There's more than one way to do things | |
| PerlMonks |
comment on |
| ( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
|
Why would nested modifiers be too hard to read? Billions of people around the world manage it on a daily basis, in human languages. I, for one, am constantly frustrated by the fact that simple, perfectly readable things like print if /foo/ while <$fh>don't work. This to me is more intuitive than either of the alternatives, namely /foo/ and print while <$fh>which messes up the order of operations, or while (<$fh>) { print if /foo/ }which is certainly clear, but just looks cluttered with all that extra punctuation. Your argument that nested modifiers would be hard to read is weakened by the fact that the "and" version, which is supported today, is by far the least readable of the three. I'm sure I'm not the only average Perl hacker who has to think twice to be certain that the "while" and "and" will be evaluated in the correct order... In reply to Re^2: what would you like to see in perl5.12?
by Porculus
|
|