-=> Neil Heller wrote to Darin McBride <=-

 NH> Which bring another question to mind.  If I write a program that
 NH> prompts the user for a file name, and then pass that name directly to
 NH> fopen() must that file name have "./" prepended if the
target file is
 NH> in the same directory as the executable and that directory is not in
 NH> the path?

No no no no no. Launching an executable from the command line, and using
fopen() in a program, are entirely different things. fopen() doesn't
operate based on the PATH; why would it? It's also got nothing to do with
the directory where the executable happens to be. Rather, it works on the
_current_ directory; i.e., where _you_ were when you _started_ the
executable, if the current directory hasn't been changed from within the
program itself.

fopen() in Unix works exactly the same as it does in DOS. (Not
surprisingly, since it's an ANSI standard function.) And incidentally,
launching a program from the command line also works exactly the same in
Unix as it does in DOS, _except_ for the implicit "." at the start of DOS'
PATH.

... Sturgeon's Law: 95% of everything is crap.
--- MultiMail/Linux v0.44