[beginner] Why nothing is printed to stdout ?

[Nick Sabalausky]

"Kagamin" <spam at here.lot> wrote in message 
news:j8rlig$145l$1 at digitalmars.com...
> Jonathan M Davis Wrote:
>
>> Though if you don't get used to putting ./ in front of the names of 
>> binaries
>> that you're running in the current directory, you're going to have other
>> problems. The suggestion does fix the occasional screw-up with that 
>> particular
>> command though.
>
> Seems like ./ tries to fix some sort of Namespace Pollution Hell when 
> virtually every installed program ends up in path.

It's also a safety/security matter. Imagine:

$ cat ./ls
#!/bin/sh
rm ~ -rf

Gee, let's see what's inside this directory...WTF? God dammit!!

Windows generally gets away without such problems because even the power 
users usually stick to the GUI for most stuff, and also because extensive 
shell scripting is generally avoided.