J
Jean Charbonneau
I think you're confusing "system calls" (either when they're invoked
directly from a C/C++ program, or as a result of running command
interpreters' "built-in" commands such as cd on Win/Unix, del on Windows,
etc.) with the running of "external" or "transient" commands. Since, under
Windows, even the command line's "del" is built in to the command
processor, it wouldn't rely on the setting of PATH (which, under Windows,
is used primarily to locate executable commands in the case when they're
not present in the current working directory). In any case, library
functions such as "remove" would never in their right mind invoke a
command processor, since removing is a system API facility that can be
invoked directly via a direct API call...again, without any use for the
PATH setting. In fact, I doubt any library functions ever have any need to
invoke the command processor, with the exception of those designed
specifically for the purpose of invoking a command processor with various
configurations of arguments. Those, such as system(), would be the only
ones that the PATH setting might affect.
-leor
--
Leor Zolman --- BD Software --- www.bdsoft.com
On-Site Training in C/C++, Java, Perl and Unix
C++ users: download BD Software's free STL Error Message Decryptor at:
www.bdsoft.com/tools/stlfilt.html
Yes you are totally right, I had a confusion there, thank you for making it
clearer!