Mail Archives: djgpp/1997/04/06/11:27:36
From: | noone AT nowhere DOT org (Omnichron)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Trouble With Globbing
|
Date: | Sun, 06 Apr 1997 14:25:09 GMT
|
Organization: | HyperLight Concepts
|
Message-ID: | <3347afbf.1493961@news.erols.com>
|
NNTP-Posting-Host: | col-as6s56.erols.com
|
Mime-Version: | 1.0
|
Lines: | 29
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Desperate plea for help: Can someone please either tell me how
to quickly and easily disable filename globbing in DJGPP or provide me
with a replacement __crt0_glob_function? I'm working on sort of a
front-end to the DOS MOVE command that smartens it a bit, and I had it
working just fine under Borland Turbo C/C++ 3.0. I decided to
recompile it under DJGPP to take advantage of the flat memory model
and LFN support, but after I finally got DJGPP, INFO, RHIDE, and all
the rest working, I started getting error messages from the program
(really from MOVE, I think) that read something like "Too many
parameters - ..\maxhead.ico." After I bit of checking, I found that
instead of passing "..\*.ico" to MOVE, it was getting passed a big
string.
It would be relatively easy to work around this (just run MOVE
separately for each file), except for the fact that argv[1] and
argv[2] have suddenly become strings of pathnames/filenames separated
by spaces. I really don't feel like writing extra code to parse these
blocks, plus I'm not sure how to do it. If I can't find a way to
disable globbing, I'm afraid that I'm going to have to abandon my
project entirely until I can afford to buy the latest version of
Borland C that includes a 32-bit DOS development kit. Mucho thanks in
advance to anyone who can help me.
More Dilbert Wisdom:
"Stupidity is like nuclear power; it can be
used for good or evil."
"...And you don't want to get any on you."
- Raw text -