Xref: utzoo comp.lang.c:26598 comp.software-eng:3073
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!mintaka!mit-eddie!apollo!apollo.hp.com!spicer
From: spicer@apollo.HP.COM (Steve Spicer)
Newsgroups: comp.lang.c,comp.software-eng
Subject: Re: C Community's Cavalier Attitude On Software Reliability
Message-ID: <49051a20.20b6d@apollo.HP.COM>
Date: 5 Mar 90 22:58:00 GMT
References: <802@xyzzy.UUCP> <8230@hubcap.clemson.edu> <255@emdeng.Dayton.NCR.COM>
Sender: root@apollo.HP.COM
Reply-To: spicer@apollo.HP.COM (Steve Spicer)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 13

This 'discussion' sometimes seems more suited for alt.comp.religion than
anywhere else.  Therefore...

Mr. Wolf, I'd love to give up C and learn a new language, so please
name one for which the following statement is true:
"If it compiles, it must be correct."  Don't bother with C, Ada, Modula-2,
Pascal,FORTRAN,COBOL,Lisp,Prolog,Basic, or PL/1 -- I've seen programs
in each where the compiler did what the programmer said instead of
what the programmer meant.  I've blamed lousy training, lousy
documentation, lousy specs, and occasionally not enough sleep, but I
have NEVER blamed the language for my own shortcomings.

Steven Spicer