> Do you remember any C library function that does a fprintf(stderr)? Or a
> Windows API function that pops up a MessageBox() in an error case? Or a
> Java API class that displays a JOptionPane.showMessageDialog()?
And how many of those functions should have such warnings? Probably a lot! If
you were to call memset(NULL, 0, 256), what should be the correct behavior? For
a dialog to appear saying that NULL was passed when it shouldn't have been, or a
Sad Mac or UAE dialog to appear? I can't see why anyone wouldn't prefer the
former.
> Grepping the 3.0 PalmOS sources reveals hundreds of
> ErrFatalDisplayIf()s. Having to program around these makes life as a
> Palm developer much harder than it should be.
Well, if you weren't programming around the ErrFatalDisplayIfs, then you'd spend
your time programming around random system crashes, and without the benefit of
an error message telling you what went wrong.
-- Keith