On Mon, May 16, 2016 at 12:45 PM, Johannes Schindelin <[email protected]> wrote: > On Mon, 16 May 2016, Eric Sunshine wrote: >> On Mon, May 16, 2016 at 9:16 AM, Johannes Schindelin >> <[email protected]> wrote: >> > On Mon, 16 May 2016, Eric Sunshine wrote: >> Agreed. Specific to the "established previously" I wrote above, I was >> referring to [1] from just a few days ago which explained why 'return >> -1' was preferable to die() in a similar case that had an odd mix of >> 'return -1' and die() in the same function. >> >> [1]: >> http://thread.gmane.org/gmane.comp.version-control.git/289476/focus=293556 > > Yes, this is an excellent link. Maybe we would want something like this, > too? > > -- snipsnap -- > diff --git a/Documentation/CodingGuidelines > @@ -333,6 +333,10 @@ For C programs: > + - Use die() only to signal an exceptional conditions which should > + abort the program. All other error conditions should instead > + return e.g. using "return error(...)".
Hmm, the bit you said earlier about "library" code vs. end-user code would be important, too, I'd think. Also, I'd expect that this sort of thing is implicitly understood by most programmers, and as this is only the first time (in recent memory) that it has needed explanation on the mailing list, I'm not sure that it deserves explicit mention in CodingGuidelines (but perhaps I'm not a good judge of these things). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
