News for hackers. Stuff that matters.

A comment on GCC undefined behaviors are getting wild. Parent comment

Re:GCC undefined behaviors are getting wild by xigoi on Monday November 28, 2022 @09:08AM (#33773781)
> The contract is that libX_foo can return null.

I'd expect any reasonable library to say “libX_foo returns null if [something happens]”. What use is there in a procedure that can just return null whenever it feels like it?

[ Parent | on HN ]
Re:GCC undefined behaviors are getting wild by account42 on Tuesday November 29, 2022 @04:20AM (#33785374)
It returns null when it fails to do its task for some reason. It is not unreasonable for the condition for that failure to be complex enough or change over time so it doesn't make sense to spell it out in the interface contract.
[ Parent | on HN ]