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,30e3597af28a3026 X-Google-Attributes: gid103376,public From: "William B. Clodius" Subject: Re: Simple algorithmic question I hope :-) Date: 1999/11/03 Message-ID: <3820603B.1E9C108F@lanl.gov>#1/1 X-Deja-AN: 544000561 Content-Transfer-Encoding: 7bit References: <7uuuba$8s4$1@nnrp1.deja.com> <19991025071337.29192.00000857@ng-fa1.aol.com> <7v255q$eth$1@nnrp1.deja.com> <7va4ns$898$1@nnrp1.deja.com> <7vhirl$92q$1@nnrp1.deja.com> <7vhrs6$79q1@news.cis.okstate.edu> <7viqum$3bd$1@nnrp1.deja.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@lanl.gov X-Trace: newshost.lanl.gov 941645883 14811 128.165.58.113 (3 Nov 1999 16:18:03 GMT) Organization: Los Alamos National Laboratory Mime-Version: 1.0 NNTP-Posting-Date: 3 Nov 1999 16:18:03 GMT Newsgroups: comp.lang.ada Date: 1999-11-03T16:18:03+00:00 List-Id: Robert Dewar wrote: > > > Well I was of course referring to the most recent version. Of > course Fortran is really odd, both the 77 and 90 standards > from ANSI are valid at the same time, a very peculiar situation > reflecting an inability to get a real consensus that F90 > represented *the* direction in which Fortran development should > go. Does someone know if the ISO standard suffers the same > schizophrenia? Normally there can be only one ISO standard for > a language (Ada 83 is no longer an ISO standardized language). > No, ISO recognized only one standard. The US appears to have been the only country that retained both standards as applicable. I believe this dual standard ended in 1996 or 1997, shortly before Fortran 95 became a standard. Politically this was justified as driven by the NIST conformance tests for Fortran 77 which was odd because 1. Fortran 90 was to all intents and purposes a superset of Fortran 77 + MIL-STD 1753. About the only problems the test code could have is if the test code were not valid, or they used a name for a procedure that was identical to one of the new intrinsics added in Fortran 90, a conflict that is easy to fix using the EXTERNAL statement and still leave the test code valid Fortran 77. 2. Most compiler implementors that I have talked to, more than half a dozen, talked about the conformance tests as if they were a joke. 3. By 1995 NIST was talking about getting out of programming language conformance testing activity. In reality it was driven by the large number of Fortran 77 vendors, more than half the total, that either could not afford to upgrade their compilers to standard conformance or wanted to focus on other areas (e.g. Watcom and C/C++) but still wanted to tout their compiler as standard conforming.