Mostly security though…Your friendly neighborhood sysadmin has ‘.’ in his
path…you have a binary ‘ls’ in your homedir. “Hey sysadmin, could you
look at this weird file in my home dir?” and the next thing you know, you’re
“Adam Mallory” <email@example.com> wrote in message
You should always need to do a ./ (unless it’s a tool on your path).
Having the current directory as part of your path is bad, especially when
you enter a directy containing binaries for a different platform, with the
same name as your toolset (ie. ls, pidin etc).
QNX Software Systems Ltd.
[ > firstname.lastname@example.org > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> email@example.com
“Kris Warkentin” <> firstname.lastname@example.org> > wrote in message
news:a2hf1k$ase$> email@example.com> …
I can’t tell you how many times I’ve done that…> > Now I’ve got “./”
programmed into my fingers like “:wq”
“Igor Kovalenko” <> firstname.lastname@example.org> > wrote in message
news:a2fan7$eoc$> email@example.com> …
Aren’t you calling your program ‘test’ ? >
If you do, try to remember first basic rule of Unix programming: do
your test program ‘test’, because ‘test’ is name of shell built-in
(which prints nothing).
“Jean-Sebastien Perron” <> firstname.lastname@example.org> > wrote in message
news:a206jt$hrb$> email@example.com> …
I have a AMD 1400 Mhz and 256 Meg.
The program is a hello.cpp file made with “ped”
it use stdio lib and printf(). (as the help tutorial)
I compile it with QCC
No warning or error (in fact no message)
NB: if i put error in my code, there is error messages.
The new file exec is created
But i am not able to execute it.
QCC is set properly set to -V x86 by default
Thank you for your time.