I said I believe this is a problem that's caused by bad naming conventions.
If you need to rely on proper variable names to recognize a construct as what it is (like you seem to imply), then the syntactic distinctions (here: presence or absence of a comma) between the constructs is too small.
The reason is that when you debug stuff, you can't rely on the fact that code you read is sane or correct.
What's your actual code?
One piece that caught my eye in the grep/ack output was print $response, $/;
Which (when read inaccurately) could either print to a response file handle, or print a response.
And don't tell to call that variable $response_fh instead if it's a file handle. For foreign code I have no influence on the naming, and I don't like that for my own code. If I want type annotations, I use a statically typed language which actually checks the type.
In reply to Re^6: curly braces around a lexical file handle
by moritz
in thread curly braces around a lexical file handle
by rastoboy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |