On 10/25/2010 01:39 PM, micah anderson wrote: > Capturing the return code of every call and making sure it is what is > expected isn't particularly onerous, its actually good practice. The > fact that its not done, and instead "set -e" is used instead, is the > reason why it seems onerous now.
i believe the current monkeysphere code actually does this in most
circumstances. set -e is currently there to catch things like failures
within pipelines (we're also using set -o pipefail), and there are
several places we use traps alongside set -e as a shell-based
(POSIX-compliant, i believe) exception-handling mechanism.
My point here is to say that we are not currently blithely ignoring
errors; I believe we're checking them appropriately where mitigating
techniques are possible. That said, patches are welcome.
--dkg
signature.asc
Description: OpenPGP digital signature
