Important Notice
The pages on this site contain documentation for very old MS-DOS software,
purely for historical purposes.
If you're looking for up-to-date documentation, particularly for programming,
you should not rely on the information found here, as it will be woefully
out of date.
Expanding Wild-Card Arguments
◄Up► ◄Contents► ◄Index► ◄Back►
────────────────────────────────────────────────────────────────────────────
You can use the wild-card characters──the question mark (?) and
the asterisk (*)──to specify file-name and path-name arguments on
the command line.
Command-line arguments are handled by a routine called _setargv,
which by default does not expand wild cards into separate strings
in the argv string array. You can replace the normal _setargv with
a more powerful version that does handle wild cards by linking
with the SETARGV.OBJ file. See the example program TYPEIT.C for
an example of wild-card processing.
You can link with SETARGV.OBJ in the PWB environment by adding
SETARGV.OBJ to the program list for your program. You must specify
the complete path or put SETARGV.OBJ in the current directory.
You must also turn off the Extended Dictionary flag within the
PWB environment, or use the /NOE linker option outside the
environment. For example,
cl typeit.c setargv /link /NOE
The wild-card characters are expanded in the same manner as in
MS-DOS or OS/2. (See your DOS user's guide if you are unfamiliar
with these characters.) Enclosing an argument in quotation marks
(" ") suppresses the wild-card expansion. Within quoted arguments,
you can represent quotation marks literally by preceding the
double-quotation-mark character with a backslash (\).
If no matches are found for the wild-card argument, the argument
is passed literally.
See also: ◄Suppressing Command-Line Processing►
◄Parsing Command-Line Arguments►
-♦-