From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,d901a50a5adfec3c X-Google-Attributes: gid103376,public X-Google-Thread: 1094ba,9f0bf354542633fd X-Google-Attributes: gid1094ba,public From: dewarr@my-dejanews.com Subject: Re: Fortran or Ada? Date: 1998/09/25 Message-ID: <6uh8ph$1el$1@nnrp1.dejanews.com>#1/1 X-Deja-AN: 394895143 References: <36068E73.F0398C54@meca.polymtl.ca> <6u8r5o$aa4$1@nnrp1.dejanews.com> <360A3446.8AD84137@lmco.com> <6udre0$ha1$1@nnrp1.dejanews.com> <6uenmo$fov$1@nnrp1.dejanews.com> X-Http-Proxy: 1.0 x3.dejanews.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja News - The Leader in Internet Discussion X-Article-Creation-Date: Fri Sep 25 23:25:38 1998 GMT Newsgroups: comp.lang.fortran,comp.lang.ada X-Http-User-Agent: Mozilla/2.02 (OS/2; I) Date: 1998-09-25T00:00:00+00:00 List-Id: In article , eachus@spectre.mitre.org (Robert I. Eachus) wrote: > In article <6uenmo$fov$1@nnrp1.dejanews.com> dewarr@my-dejanews.com writes: > > > My best understanding is that the DO I = 1.6 type bug was > > actually in the code at one time, but discovered during > > simulation. > > > Incidentally there is a remarkable APAR for IBSYS Fortran > > IV dated around 1967 which read something like > > > "The Fortran compiler miscompiles [the above type of DO] > > and treats it as an assignment statement. This will be > > corrected in a future release." > > > TO my knowledge this APAR was never closed :-) > > I thought it was. Several compilers I used in that time frame would > produce warning messages if a reserved word was combined into an > identifier, or if any spaces occured in suspicious places. > (Unfortunately, I know this because I had to check all warnings on > some code which had been written with variable names containing > spaces. Fortunately, six, and later eight, character names didn't > have much room for mischief like this, but I do remember variables > named NO GO and LAST X.) Robert, I am not sure you know the terminology I am using here. IBM could hardly close that APAR, since the defect it refers to is not a defect. That's the point, there is no way that a compiler could be stopped from "misclassifying" this statement. The IBM compilers for the 7000 series (both under FMS and IBSYS) did not have warnings of the type you recall, and in any case a warning is not enough to "close" this APAR! By the way, Fortran II had a genuine language ambiguity READ TAPE2, X, Y, Z to read from variable format variable TAPE2 READ TAPE 2, X, Y, Z to read from tape unit number 2. Remember that blanks were insignificant in Fortran II. An undocumented feature was that the Fortran II compiler always chose the second possibility! -----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum