Re: command line processing question
"Gianni Mariani" <gi3nospam@mariani.ws> wrote in message
news:46ecbc3d$0$32452$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
News wrote:
...
Any help is much appreciated!
a) There is a standard program called - you guessed it - "test" on some
systems so it's a bad idea to write your own.
b) You need to check that your command line processor is looking in the
right directory for your executable. This is usually in the path or PATH
environment variable.
c) You can specify the fully qualified name to your executable file. e.g.
./test or .\test depending on os
d) various IDE's will place your executable in wierd places like Debug,
Release, work.gx86_32 etc. Make sure you know where it is being created.
a) Is interesting. Since the very first time I got on a unix box I decided
to write a test program in c and called it test.c For an hour I kept trying
to figure out why my program wouldn't output anything no matter how many
times I modified it. Finally I got fed up, deleted my program and ran test
just to make sure it would give me an error, which it didn't. It came back
with the prompt. His eyes open wide. Sure enough, there was a system
command called test, and in this version of unix (if not all) the local
directory was checked after the system directories. Lesson learned.
b/c) Is probably what's happening this person since windows is giving him a
command not recognized. Most likely my guess is he's using some version of
VC++, is in the path of his .cpp file, but isn't aware that his program
actually gets compiled into a subdirectory debug or active. I suspect
debug\test Mike
would probalby do it for him.