Gerhard Fiedler wrote:
> Dave Tweed wrote:
> > Yes, on an archaic system like the Windows command-line processor (which
> > has distant roots in the original CP/M CCP), the application programs
> > must do some of the work of handling the "raw" command line. 
> 
> Are you sure about this? When was the last time you wrote a CLI program on
> Windows where you had to handle the raw command line and didn't have access
> to an array of parsed command line arguments? What language did you use?

I never have. YOU'RE the one who said that applications built to work with
Windows shells need to handle quoted arguments.

I assume that the command-line handling is hidden in run-time libraries
that come with the software development environments for Windows.

Pretty much all of the command-line software I write for Windows is done
either in Perl or gcc, which are the same thing, really, when it comes to
handling the command line.

But I gave up on the MS command line long ago, first with DJGPP bash, and
more recently with Cygwin bash. The only time I need to work with cmd.exe
(and nested .BAT files) is in Olin's build environment for PIC software.

-- Dave Tweed
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist