Re: command line processing question
On Sep 16, 12:05 pm, "Jim Langston" <tazmas...@rocketmail.com> wrote:
"Gianni Mariani" <gi3nos...@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 PA=
TH
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 create=
d.
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.
Don't feel bad. I still get caught out by the built in
occasionally, and I've worked almost exclusively under Unix for
over 20 years. Of course, ./test works. (And if you compile by
simply invoking "CC test.c", the name of the executable is
a.out.)
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.
The order directories are checked depends on the $PATH variable
(the same as in Windows, I think). The problem is that test is
(usually) a shell built-in, so the shell doesn't even look in
any of the directories.
b/c) Is probably what's happening this person since windows is giving him=
a
command not recognized.
From the way he formulated his question, it sounds more like he
doesn't even know that he needs to compile the code. (He's at
the command prompt, which suggests that he isn't even in Visual
Studios. Otherwise, he'd have invoked the program from Visual
Studios, and probably be complaining that the Window was being
closed too soon:-).) If that's the case, it should be
sufficiant that he invoke "cl test.cc" before trying to execute
(and I would still use the relative pathname, .\test, rather
than counting on whatever shell he's using to not have test as a
builtin, and to look first in the current directory).
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34