Re: Parallel FORTRAN bite

sampson@cod.nosc.mil (Charles H. Sampson)
Mon, 11 Jun 90 19:17:54 GMT

          From comp.compilers

Related articles
Parallel FORTRAN bite pardo@june.cs.washington.edu (1990-05-30)
Re: Parallel FORTRAN bite sampson@cod.nosc.mil (1990-06-11)
Re: Parallel FORTRAN bite hirchert@ux1.cso.uiuc.edu (1990-06-12)
Parallel Fortran bite worley@compass.com (1990-06-20)
| List of all articles for this month |

Newsgroups: comp.lang.misc,comp.compilers
From: sampson@cod.nosc.mil (Charles H. Sampson)
References: <1990May31.161025.3138@esegue.segue.boston.ma.us>
Date: Mon, 11 Jun 90 19:17:54 GMT
Organization: Naval Ocean Systems Center, San Diego
Keywords: Fortran



In article <1990May31.161025.3138@esegue.segue.boston.ma.us> pardo@june.cs.washington.edu (David Keppel) writes:
> DOALL I = 1, N
> [appeared to the Connection Machine compiler to be]
> DO ALLI = 1, N


          Just to clarify a "fine" point, in ANSI FORTRAN '77, the construct


                                                          DOALLI=1,N


(spaces are null in FORTRAN) is defined to mean


                                                      DO ALLI = 1, N


(spaces are still null, but I hope my meaning is clear). Therefore, the
so-called DOALL extension has changed the semantics of standard FORTRAN,
rather than extending the language. The shuttle people might have a right
to be peeved, but they shouldn't direct their displeasure at the CM FORTRAN
implementors.


[I agree, adding ambiguous syntax that can change the meaning of an existing
legal program is not good language design. The entire issue of parallel
extensions to Fortran and to C is a hot topic -- I get lots of interesting
mailings from the Numerical C Extensions Group. -John]
[From sampson@cod.nosc.mil (Charles H. Sampson)]
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.