Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site ucsfcgl.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!ucbvax!ucsfcgl!kneller From: kneller@ucsfcgl.UUCP (Don Kneller%Langridge) Newsgroups: net.micro.pc Subject: Re: conventions regarding quoted arguments to DOS commands Message-ID: <535@ucsfcgl.UUCP> Date: Sun, 9-Jun-85 05:03:17 EDT Article-I.D.: ucsfcgl.535 Posted: Sun Jun 9 05:03:17 1985 Date-Received: Tue, 11-Jun-85 08:46:18 EDT References: <715@pyuxqq.UUCP> <646@digi-g.UUCP> Reply-To: kneller@ucsfcgl.UUCP (Don Kneller) Organization: UCSF Computer Graphics Lab Lines: 38 Keywords: MSC In article <646@digi-g.UUCP> dan@digi-g.UUCP (dan) writes: >In article <715@pyuxqq.UUCP> ral@pyuxqq.UUCP (R A Levenberg) writes: >it. It is code that is added by the C compiler that is doing the parsing >before calling main() of the application. So it is up to the C compiler >to recognize quotes. Your above example works fine under DOS if you use >the MS version 3 C with "...". It doesn't recognize '...'. Also, "s will >prevent DOS from acting on <, > and |. > >>A related question is the evalution of, say, *.c, on a command line. >>DOS (actually command.com) will tell the invoked program its argument >>is "*.c", whereas the UNIX shell will tell the invoked program its arguments >>are, say, main.c, foo.c and bar.c. Does this mean that DOS programs >>use those SYSINT system calls themselves to get first matching file name >>and next matching file name whenever an argument contains wild card >>characters? > >Afraid so. I heard a rumor once that the MS ver 3 C would expand match >characters. I've tried it, and it doesn't. > >Dan Messinger >ihnp4!umn-cs!digi-g!dan Sorry to differ with you Dan, but MSC version 3.0 DOES do wildcard matching but you have to link in a 'varargs.obj' file that comes with the compiler. Then *.c expands to all .c files in your current directory. Since the expansion is done after the commandline is passed to your program, this is also a way to get around the 127(?) character command line limit. As is also mentioned above, MSC also correctly handles a command line argument like "a b c". Don Kneller UUCP: ...ucbvax!ucsfcgl!kneller ARPA: kneller@ucsf-cgl.ARPA If your mailer has trouble with the above Arpanet address, try: @berkeley.arpa:kneller@ucsf-cgl.arpa