> that's a slightly different aspect. the note should not be "page fault" but > "out of memory" (or some such thing). that's much better than a nil return. > most errors on shared resoruces are better expressed as exceptions (notes), > because that's what they are: they are a failure of the underlying physical > or virtual machine > to handle an exceptional case. the code shouldn't have to deal with it > explicitly everywhere, > except in C to detect and propagate the exception to code that knows what's > going on.
if one wishes to be remotely standards-compliant, sending a note on allocation failure is not an option. k&r 2nd ed. p. 252. - erik
