On 24/02/2013 12:03 PM, Warp wrote:
> Orchid Win7 v1<voi### [at] devnull>  wrote:
>> I agree. However, unfortunately it seems that by default Bash ignores
>> all such errors and happily proceeds, unless you manually suffix every
>> single command with an explicit return-code check.
>
> How is that different from any programming language?

In C#, Java or similar, if you try to open a file and can't, an 
exception is thrown, and your program is halted. (Unless you thought of 
that eventuality and coded a catch{} block for it.) In Bash, the program 
continues to execute as if everything worked just fine, silently 
ignoring the error.

Post a reply to this message