Re: Strings in Cray namelists?

Steve Lionel <steve.lionel@xxxxxxxxxxxxx> wrote:

Bil Kleb wrote:

reveal that only Portland, PathScale, and NAG are standards compliant:

Adopting an extension is not a violation of the standard. I don't think
you can accuse a compiler of being non-compliant because it actually
works on a program. There are cases where at least a diagnostic
capability is required, but this isn't one of them.

No, your test simply reveals that the compilers you use do not support
the Fortran 2003 feature of reading undelimited character strings from
NAMELIST input, as long as they do not contain embedded delimiters.
That PGI and Pathscale have this issue does not astonish me, but that
you see it with NAG does.

Are you sure that this f2003 feature applies to namelist? I know about
it for list-directed I/O. At a (very) quick glance, I didn't see it for
namelist. I might well have missed it, but I also wouldn't take for
granted that just because it applies to lisy-directed, that
automatically also means namelist. The two have many similarities, but
namelist does have a few extra issues that one might see as complicating
it.

I don't use namelist any more myself, so I tend to have to read this
stuff pretty carefully. Oddly, I stopped using namelist just a little
before it became standardized. That was because around then I started
using a library of routines that allowed simillarly human-readable
input, but with much more flexibility of form.

--
Richard Maine
email: last name at domain . net
domain: summer-triangle
.

Relevant Pages

  • Re: Name a good Vista feature that goes beyond whats in Tiger.
    ... Some have a use for such apps due to work and such. ... dock and annoy the crap out of you. ... it isn't a feature of the OS: ... H.264 and mpeg4 are standard formats. ...
    (comp.sys.mac.advocacy)
  • Re: What could J4 (or WG4) do (was: INSPECT and TRAILING syntax
    ... They will happily sit on a committee and protect their strategic COBOL ... What a given implementor will provide as feature content in a COBOL compiler ... Well, as I said in another part of this thread, I think the standard has ... I disagree that it has no value without a regression suite. ...
    (comp.lang.cobol)
  • Re: Language standard: the least common denominator vs. utility
    ... ISO/ANSI C standard to define capabilities relevant for computers ... we haven't configured any IPv6 interfaces. ... this feature even though the system supports it". ... there should be "versions" of the feature test ...
    (comp.lang.c)
  • Re: Complex question
    ... The appropriate question when considering adding a feature to the ... The complex types are arithmetic types, with a full set of arithmetic ... are not lvalues. ... IMHO that's too messy to seriously consider adding to the standard. ...
    (comp.lang.c)
  • Re: Mutual derived type dependencies
    ... not make an exception for allocatable here. ... a new feature request. ... ends up messsed up in the published standard (or if it is messsed up ... the final yes/no vote on the standard comes out as "no"). ...
    (comp.lang.fortran)