But it's worth noting an "inconsistency" when printing to filehandles, since
is an everyday use of indirect object notation (same with say )
So common that no feature "indirect" won't disable it.
This will also answer the question, how to add arguments to such a method call:
Drop the comma between object/class and first argument.
Now I'm curious to know how the very common
is effected by this feature.
Brian's article says that new is also forbidden!
Which makes sense since it's not a keyword, you can name the constructer(s) freely.
But it also claims that filehandles are generally exempted, which would also cover flush...
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
In reply to Re: Why does "flush filehandle" work? (indirect object)
by LanX
in thread Why does "flush filehandle" work?
by chengiz5
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |