Safe coding practices

[Garrett Wollman]

In article <1074 at mwtech.UUCP> martin at mwtech.UUCP (Martin Weitzel) writes:
>RIGHT! Don't assume anything that *can* fail will *not* fail in your
>particular case. (And don't apply "logic" - there may be reasons you can't
>see right now because they are outside the range of your experiences.)
>-- 
>Martin Weitzel, email: martin at mwtech.UUCP, voice: 49-(0)6151-6 56 83

This reminds me of the origin of the Andrew Message System.  CMU
developed AMS chiefly because, with AFS (then the Andrew File System
and before that VICE), it is now possible for close() to *fail*.
Since most programmers (including the ones responsible for the
standard MUAs and MTAs on their target hosts) operated under the
assumption that it is impossible for a close() to have a soft failure,
they had to develop a message system that was reliable in instances
where close() *could* fail.

-GAWollman

Garrett A. Wollman - wollman at emily.uvm.edu

Disclaimer:  I'm not even sure this represents *my* opinion, never
mind UVM's, EMBA's, EMBA-CF's, or indeed anyone else's.