3 ms·

I think this is actually an artifact of the 'check the single return value for errors' that requires that the return domain contain at least one error code poin

I think this is actually an artifact of the 'check the single return value for errors' that requires that the return domain contain at least one error code point. how else you might structure errors without changing much of the rest of C left for an exercise

amenghra 4y ago
just require the programmer to check errno after every function call? /s
- convolvatron 4y ago
  omg. I forgot about that. the one thing even worse than overloading the return domain.
  - kilgnad 4y ago
    Bit my company in the ass recently we uncovered a bug that was causing us to lose 20% of our data for a year. sqlite C libraries apparently still do this. The person who wrote the code was both not very good and had no idea that an error was even occuring.
    - amenghra 4y ago
      Blame the lack of a proper linter instead of blaming the person who wrote the code?
      - kilgnad 4y ago
        There's no linter that checks for a missing if statement and a missing error handler.
- Gibbon1 4y ago
  Strange but true you can create functions where you pass a pointer to an error variable. error_t oops; int x = foo(10, &oops); if(oops) goto whoops; int x = foo(10, 0); // yolo!