Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site kontron.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!pesnta!pertec!kontron!cramer
From: cramer@kontron.UUCP (Clayton Cramer)
Newsgroups: net.micro.pc
Subject: Re: conventions regarding quoted arguments to DOS commands
Message-ID: <214@kontron.UUCP>
Date: Mon, 10-Jun-85 12:12:05 EDT
Article-I.D.: kontron.214
Posted: Mon Jun 10 12:12:05 1985
Date-Received: Tue, 11-Jun-85 05:03:16 EDT
References: <715@pyuxqq.UUCP> <646@digi-g.UUCP>
Organization: Kontron Electronics, Irvine, CA
Lines: 19

> >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

MS ver 3.0 C does expand match characters, but you have to link your
program with SSETARGV.OBJ (or the medium or large equivalents) for the
wild card arguments to expand.  It does work; I wrote a program to do
verified erases (query user on each file, asking if he wants to delete
this file) using this facility.