> You write a batch file and run it at the command prompt -- or in the
> batch debugger, which is easier & more powerful than trying to run a
> complex command at the command prompt.
The ability to do things directly from the command line is why I use perl -e
multiple times a day. I've typed in countless FOR loops at the command line.
For one-shot tools, until the perl -e commands or FOR loops get very
complex, I simply up-arrow iterate over the line I'm building.
There must be a compelling reason to prohibit the usage at the command line
-- your position is that it is easier and more powerful for the user to
create a one-shot temporary file, but this user (and it sounds like Steve,
also) does not agree.
In fact, I use precious few _new_ batch files, which is why I don't use the
DO loop. As soon as it becomes available at the command prompt, I'll use it.
The old batch files I do use are almost all required to be CMD compatible,
so the one place I could use DO is the interactive prompt.
In order to use DO: You are suggesting I should fire up the editor, make a
new batch file, type in my desired DO, switch back to TCC, run the tool
once, delete the batch file, close the editor. If DO were available at the
prompt, I would eliminate most of those steps.
What is the compelling reason to prohibit certain constructs at the
interactive prompt? My own guess would be the parsing nightmares that you've
described.
