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: "Howard W. LUDWIG" <howard.w.ludwig@lmco.com>
Subject: Re: Fortran Namelist Package
Date: 2000/07/11
Message-ID: <396B87FB.1043DE8C@lmco.com>#1/1
X-Deja-AN: 645199841
Content-Transfer-Encoding: 7bit
References: <cQFa5.24646$L8.82219@east3.usenetserver.com>
X-Accept-Language: en,pdf
Content-Type: text/plain; charset=us-ascii
Organization: Lockheed Martin -- Information Systems Center
Mime-Version: 1.0
Newsgroups: comp.lang.ada
Date: 2000-07-11T00:00:00+00:00
List-Id: <comp.lang.ada>

"Anthony E. Glover" wrote:

> Does anyone know of an Ada package for interfacing to Fortran namelist
> files.
> I need something that can read the files and provide an interface for
> retrieving
> the values.
>
> Tony

Was NAMELIST standardized in Fortran 90?  I'm not aware that it was.
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.)

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.

Howard W. LUDWIG