News for hackers. Stuff that matters.
Re:fork() can fail by davvid on Wednesday August 20, 2014 @10:51PM (#8205738)
Yes. Always chain sequential commands with &&. Always.

This style is pretty prevalent when writing test cases in shell (or just shell scripts in general), e.g. when using something like sharness[1].

[1] https://github.com/mlafeldt/sharness

Re:fork() can fail by pimlottc on Thursday August 21, 2014 @01:07AM (#8205992)
"bash -e" has much the same effect: it basically exits on the first failed command, with considerations for pipelines, conditionals and the like.

http://www.gnu.org/software/bash/manual/bashref.html#index-s...

Re:fork() can fail by pflanze on Thursday August 21, 2014 @01:32AM (#8206036)
Note this recent discussion about bash -e, including my post that "the disappointment with set -e is that it does not work everywhere".

https://news.ycombinator.com/item?id=8054440

Re:fork() can fail by blueskin_ on Thursday August 21, 2014 @04:32AM (#8206433)
It's nice to have, but I wouldn't rely on it to save me - it's no replacement for checking return codes properly.
Re:fork() can fail by pimlottc on Thursday August 21, 2014 @07:52PM (#8210308)
Certainly, but it's a good habit to get into, like ``use strict`` in Perl.
Re:fork() can fail by blueskin_ on Friday August 22, 2014 @06:20AM (#8211519)
"Perl and line noise are distinguishable. Properly written perl starts with 'use strict'; line noise rarely does."
Re:fork() can fail by stingraycharles on Thursday August 21, 2014 @12:38AM (#8205953)
When writing test cases in shell, you generally just implement a die() function and execute all commands `foo || die "bar"`
Re:fork() can fail by nitrogen on Thursday August 21, 2014 @12:41AM (#8205957)
If you don't need to specify a custom message, you could also use "set -e" to die automatically on command failure and use "trap ... EXIT" to display some kind of failure message.