NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/comp/lang/fortran/3339

Internet Message Format | 1992-09-01 | 7.0 KB

Path: sparky!uunet!cs.utexas.edu!sun-barr!news2me.ebay.sun.com!exodus.Eng.Sun.COM!appserv.Eng.Sun.COM!appserv!khb
From: [e-mail] (Keith Bierman fpgroup)
Newsgroups: comp.lang.fortran
Subject: Re: Help on FORTRAN 90 spec - NAMELISTs
Date: 1 Sep 92 10:19:33
Organization: Sun MegaSystems
Lines: 188
Message-ID: <[e-mail]>
References: <[e-mail]>
NNTP-Posting-Host: chiba
In-reply-to: [e-mail]'s message of 31 Aug 92 18:42:27 GMT



>I am in desparate need of the wording of the proposed FORTRAN 90 spec

It isn't a proposal, it is a standard. ISO-IEC 1539:1991.


10.9  Namelist formatting

The characters in one or more namelist records constitute a sequence
of name-value subsequences, each of which consists of an object name
or a subobject designator followed by an equals and followed by one or
more values and value separators.  The equals may optionally be
preceded or followed by one or more contiguous blanks.  The end of a
record has the same effect as a blank character, unless it is within a
character constant.  Any sequence of two or more consecutive blanks is
treated as a single blank, unless it is within a character constant.

The name may be any name in the namelist-group-object-list (5.4).

Each value is either a null value (10.9.1.4) or one of the forms:

  c
  r * c
  r *

where c is a literal constant and r is an unsigned, nonzero, integer
literal constant with no kind type parameter specified.  The r * c
form is equivalent to r successive appearances of the constant c, and
the r * form is equivalent to r successive null values.  Neither of
these forms may contain embedded blanks, except where permitted within
the constant c.

A value separator for namelist formatting is the same as for
list-directed formatting (10.8).

10.9.1  Namelist input

Input for a namelist input statement consists of:

  (1)  Optional blanks,

  (2) The character & followed immediately by the namelist-group-name
      specified in the namelist input statement,

  (3)  One or more blanks,

  (4)  A sequence of zero or more name-value subsequences separated by
       value separators, and

  (5)  A slash to terminate the namelist input statement.

In each name-value subsequence, the name must be the name of a
namelist group object list item with an optional qualification and the
name with the optional qualification must not be a zero-sized array, a
zero-sized array section, or a zero-length character string.

If a processor is capable of representing letters in both upper and
lower case, a group name or object name is without regard to case.
...

10.9.1.2  Namelist input values

The datum c is any input value acceptable to format specifications for
a given type, except for a restriction on the form of input values
corresponding to list items of types logical and integer as specified
in 10.9.1.3.  The form of the input value must be acceptable for the
type of the namelist group object list item.  The number and forms of
the input values that may follow the equals in a name-value
subsequence depend on the shape and type of the object represented by
the name in the input record.  When the name in the input record is
that of a scalar variable of an intrinsic type, the equals must not be
followed by more than one value.  Blanks are never used as zeros, and
embedded blanks are not permitted in constants except within character
constants and complex constants as specified in 10.9.1.3.

The name-value subsequences are evaluated serially, in left-to-right
order.  A namelist group object name or subobject designator may
appear in more than one name-value sequence.

When the name in the input record represents an array variable or a
variable of derived type, the effect is as if the variable represented
were expanded into a sequence of scalar list items of intrinsic data
types, in the same way that formatted input/output list items are
expanded (9.4.2).  Each input value following the equals must then be
acceptable to format specifications for the intrinsic type of the list
item in the corresponding position in the expanded sequence, except as
noted in 10.9.1.3.  The number of values following the equals must not
exceed the number of list items in the expanded sequence, but may be
less; in the latter case, the effect is as if sufficient null values
had been appended to match any remaining list items in the expanded
sequence.  For example, if the name in the input record is the name of
an integer array of size 100, at most 100 values, each of which is
either a digit string or a null value, may follow the equals; these
values would then be assigned to the elements of the array in array
element order.

A slash encountered as a value separator during the execution of a
namelist input statement causes termination of execution of that input
statement after assignment of the previous value.  If there are
additional items in the namelist group object being transferred, the
effect is as if null values had been supplied for them.

Successive namelist records are read by namelist input until a slash
is encountered; the remainder of the record is ignored.
....

The standard itself can be procured as posted in days of Yore:

From: [e-mail] (julian bunn)
Newsgroups: comp.lang.fortran
Subject: Fortran 90 Standard
Keywords: standard
Date: 13 Aug 91 06:51:57 GMT
Organization: CERN, Geneva, Switzerland




   The new Fortran 90 standard has now been formally published and is
available from the ISO central secretariat or from the national member
bodies. The price is about $120. Some ordering details follow. I can
supply addresses in other countries not mentioned on request (to
METCALF@CERNVM).

    The document reference is ISO/IEC 1539 : 1991. There is no ISBN.

    ISO
    1, rue de Varembe
    Case postale 56
    1211 Geneva 20
    Switzerland
    Fax: [phone]

    ANSI
    1430 Broadway
    New York, NY 10018

    BSI
    2 Park Street
    London W1A 2BS

    DIN
    Burggrafenstrasse 6
    Postfach 1107
    D-1000 Berlin 30

    AFNOR
    Tour Europe
    Cedex 7
    92049 Paris La Defence

    SSC
    350 Sparks Street
    Suite 1200
    Ottowa, Ontario, K1P 6N7



                            Mike Metcalf
                            (metcalf@cernvm)

and from [e-mail]

For those of you who don't read comp.lang.fortran,
you might be interested to know that I just called
Global Engineering to see if the sell ISO 1539:1991.
They do; the price is $225.

And

You can obtain copies through:
    Global Engineering Documents
    2805 McGaw Ave.
    Irvine, CA. 92714
    [phone]
    [phone]

The FORTRAN-90 standard will run you about $75 US.
--
Richard Gorton               [e-mail]  [phone]
Liant Software Corp.         Framingham, MA 01760 USA
--
----------------------------------------------------------------
Keith H. Bierman    [e-mail]| [e-mail]
SunPro 2550 Garcia MTV 12-33             | (415 336 2648) fax [phone]
Mountain View, CA 94043  <speaking for myself, not Sun*> Copyright 1992