When merlyn says, If you prompt to STDOUT, I think most people (OK I do) will read that as, If you print an interactive message to STDOUT, which is what was meant.
Furthermore the phrase ...in general indicates a confused mind... does not say that Fastolfe in particular has a confused mind. It just says that this kind of mistake is symptomatic of a confused mind. Which it is. If you do not understand how <> differs from <STDIN>, that indicates confusion! Even worse, if you meant that you expect files in @ARGV to correctly hold responses to interactive commands in a script you are still changing, that indicates dangerous programming practices!
All of which goes to say that even though I had let merlyn's post pass before, I voted ++ to counteract your -- because I thought your reasoning was not very good.
UPDATE
I have been told that "prompt" was originally "print", which shows why - particularly when a point has caused comment - it is good to make it clear that there was an edit.
In reply to RE (tilly) 4: Answer: What is a good
by tilly
in thread What is a good "Press any key to continue" code?
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |