Re: Namelist Internal Read
gary.l.scott_at_lmco.com
Date: 03/29/05
- Next message: James Giles: "Re: Namelist Internal Read"
- Previous message: Walt Brainerd: "Re: Namelist Internal Read"
- In reply to: Walt Brainerd: "Re: Namelist Internal Read"
- Next in thread: James Giles: "Re: Namelist Internal Read"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 28 Mar 2005 15:35:53 -0800
Walt Brainerd wrote:
> gary.l.scott@lmco.com wrote:
>
> > I've also never quite understood the need for the quirky &.../
syntax.
>
> It's the same reason as the inconsistent names for
> the bit intrinsics. I am not sure where namelist
> came from originally, but probably some vendor did
> it many years ago and some individual thought up
> what seemed like a neat scheme at the time.
>
> When it came up for standardization, "existing
> practice" was picked, rather than a nicer design.
>
> [Take note, ye who complain that the standards
> committee never adopts existing practice.]
>
I hate that. If there are blatantly obvious faults in the design, it
should not be adopted as-is. Vendors should define any extensions by
preceding the name with something that identifies it as an extension
(i.e. DEC_CRAY_POINTER, instead of just POINTER).
In reality, I'd just like a nice automatic text "parsing" procedure or
set of procedures that advances on namelist capabilities. I'm ok with
inputting file content through a separate read(s) and passing each
string to the parsing routine(s) preceded by a "template" of how I want
it to be parsed. The "component_name keyword=value, keyword=value,..."
part of the template is sort of obvious. It seems that you could
simply submit a derived type or several arrays to define the templates
and optional values for "substitutions" (need to define a syntax for
substitutions).
> --
> Walt Brainerd +1-877-355-6640 (voice & fax)
> The Fortran Company +1-520-760-1397 (outside USA)
> 6025 N. Wilmot Road walt@fortran.com
> Tucson, AZ 85750 USA http://www.fortran.com
- Next message: James Giles: "Re: Namelist Internal Read"
- Previous message: Walt Brainerd: "Re: Namelist Internal Read"
- In reply to: Walt Brainerd: "Re: Namelist Internal Read"
- Next in thread: James Giles: "Re: Namelist Internal Read"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|