On 6/8/20 10:02 AM, Chet Ramey wrote:
> On 6/8/20 7:24 AM, Greg Wooledge wrote:
>> This is part of the set -e nightmare, which is what we keep trying to
>> get you (and everyone else) to understand.
> 
> Most of the issue with `set -e' is folks not understanding when it's
> not in effect.

Well, Greg does have a pretty good point (which is a point I for one
prioritize in my decision process for "do I personally recommend the use
of set -e") in that another part of the issue is its doing different
things across point releases of a shell.

And that's not counting the times when the issue is people not
understanding when it *is* in effect.

Or people who know exactly when it is and isn't in effect, and have no
issue, but decline to use it because the precise nature of "when it is
and isn't in effect" decreases the usefulness of it sufficiently to make
them decide they're better off implementing error checking a different
way... and *that* is, I think, what Greg is pointing out.

-- 
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to