Re: block data and namelist

Thomas Koenig wrote:
.....
> You could put
>
> common /foo/ a
> namelist /foo_n/ a
>
> into an include file, and you could include this into a block data.

Yes, that was my theory about how your problem arose
to begin with. I was just trying to explain the motives of
the language designers. Why would you expect to be able
to make declarations that could not possibly have any meaning
in the context?

--
J. Giles

"I conclude that there are two ways of constructing a software
design: One way is to make it so simple that there are obviously
no deficiencies and the other way is to make it so complicated
that there are no obvious deficiencies." -- C. A. R. Hoare


.

Relevant Pages

  • Most-used browsers?
    ... see emerging trends in internet access. ... iPhones and other G3 devices are increasingly common. ... so simple that there are obviously no deficiencies. ...
    (comp.infosystems.www.authoring.html)
  • Re: function : question on argument for output
    ... grounds that function's sole purpose should be to calculate their ... It is of course often necessary to return error codes ... variable) is a common method. ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)
  • Re: 6 gfortran bugs
    ... > as failure to generate an executable in the presence of common ... than an error might indeed coincide with "common minor ... aren't common that only deserve warnings. ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)
  • Re: block data and namelist
    ... > Is it OK to have a namelist in block data, ... NAMELIST declaration identifies a set of variables that ... can be used in namelist I/O transfers. ... no deficiencies and the other way is to make it so complicated ...
    (comp.lang.fortran)