Adam Borowski <kilob...@angband.pl> writes: > On Wed, Sep 25, 2013 at 09:38:18AM -0700, Russ Allbery wrote:
>> Programs that don't check the return status of functions that they >> think won't ever fail are a bit of a pet peeve of mine, in part because >> it would make a lot of sense for localtime() to be able to fail when >> the question it was asked is undefined. But no one ever checks the >> return status of localtime() for much the same reason that you spell >> out for not checking the return status of crypt(), which means that >> localtime() is required by all this legacy code to return arbitrary >> nonsense instead of an error. > __attribute__((warn_unused_result)) Now that is an *excellent* idea for crypt(). In fact, I'm surprised that it's not already tagged with that attribute. I think I'll suggest that on libc-alpha. Thanks! Doing that for localtime() may be too much of an uphill climb. :/ -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87had8rgqn....@windlord.stanford.edu
