Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!ucbvax!WATSON.IBM.COM!jbs
From: jbs@WATSON.IBM.COM
Newsgroups: comp.arch
Subject: Re: IEEE arithmetic (Goldberg paper)
Message-ID: <9106282329.AA20495@ucbvax.Berkeley.EDU>
Date: 28 Jun 91 23:13:12 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 15


         I said:
:>    1.  I would not buy a compiler from someone who enjoys breaking
:>user code.
         Jon Krueger replied:
>Neither would I.
>But a compiler which exposes broken user code is a different animal.
         User code which complies with a variant or extension of the
Fortran 77 (or any other) standard may not be portable but it is not
"broken".
         The DO, ENDDO construct is not in the Fortran 77 standard.
Nevertheless many Fortran 77 compilers recognize it and many users use
it.  I would not advise omitting it from your compiler in order to
"expose" "broken" user code.
                          James B. Shearer