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,9b80b903b52ea036 X-Google-Attributes: gid103376,public From: Dan Nagle Subject: Re: Fortran Namelist Package Date: 2000/07/11 Message-ID: <396BA9F0.E69BA6E6@erols.com>#1/1 X-Deja-AN: 645250644 Content-Transfer-Encoding: 7bit References: <396B87FB.1043DE8C@lmco.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@rcn.com X-Trace: 9/1i9P1689JyA4LyX81Ml0lcBActsRU0g/Zf/aG8eqo= Organization: Purple Sage Computing Solutions, Inc. Mime-Version: 1.0 NNTP-Posting-Date: 11 Jul 2000 23:13:01 GMT Newsgroups: comp.lang.ada Date: 2000-07-11T23:13:01+00:00 List-Id: Hello, "Howard W. LUDWIG" wrote: > > Was NAMELIST standardized in Fortran 90? I'm not aware that it was. It was, and the definition was further enhanced in Fortran 95. (Comments in namelist files were added.) > I know that many compilers provided NAMELIST as extensions to > FORTRAN 66 and FORTRAN 77; however, as extensions and not part of > the standard, the implementations among vendors varied quite a bit. > (I believe DOD had NAMELIST in some MIL-STD defining Fortran for > DOD purposes, but it did not match any ISO/IEC/ANSI standard--in fact, > I suspect that DODs failure to get NAMELIST and ENCODE/DECODE approved > as part of FORTRAN 77 was part of the driving force for DOD having a > language they could exercise more control over--and they ended up > with Ada--not too shabby.) Well, ENCODE/DECODE were replaced by internal read/write when Hollerith was replaced by the character type (with f77). Mil Std 1753 was universally implemented if not adopted by ANSI. It is because, in part at least, the "details" of extensions often differ from compiler to compiler that "industry practice" isn't simply copied into the Fortran standard. It's often the semantics rather than the syntax that differs, and often only "slightly". > > In other words, you need to be careful about using such NAMELISTs in > Fortran because of the variety of syntax used by vendors. Even if you > do find existing Ada code (and I am not aware of any--have you checked > the PAL?), it may not do what you need because it supports the "wrong" > syntax. If the Ada code is newer than f95, it's probably at least trying to support the right syntax; if it's newer than f90, it may not support comments in the namelist file. If it's older than f90, it's probably trying to support Mil Std 1753. Of course, you're right to test it first ;-) Any Fortran 90/95 compiler will have a "new namelist/old namelist" switch if the vendor supplied a namelist which differed from what was standardized. > > Howard W. LUDWIG -- Cheers! Dan Nagle Purple Sage Computing Solutions, Inc.