Re: what weren't structure/union/map made part of F77/90 ?



Richard E Maine <nospam@xxxxxxxxxxxxx> wrote:

> Lynn McGuire <nospam@xxxxxxxxxx> wrote:
>
> > Since the usage of structure / record / ... is so prevalent, why haven't
> > they been added to the fortran standard ?
>
> Well, I'd say because
> [somewhat smart-alecky reply, including...]

> 2. The standard is plenty big enough...

Now that I'm home, a slight elaboration on that one. Adding structure et
al to the standard would be a *BIG* job. That's largely because it would
have to be integrated with everything else, somehow or another. Even if
the integration amounted to saying that it didn't work in conjunction
with something else, that still would have to be said, and someone would
have to figure out all the places where it needed to be said. Skim the
standard for how many places something gets said about derived types.

Not only would it be a lot of places, I think some of them would be
hard. I haven't bothered to think very hard about it, but my off-hand
guess would be that it would not integrate cleanly at all with several
other features - no I don't have, nor do I care to come up with details.

As a vendor feature hanging around several compilers for compatibility
with old code, the vendors in question can get by with just blowing off
questions that would have to be seriously addressed if it were added to
the standard. And if it were added to the standard without decent
integration, intended only to standardize old codes, then that would not
seem like an argument likely to gather much support.

--
Richard Maine | Good judgement comes from experience;
email: last name at domain . net | experience comes from bad judgement.
domain: summertriangle | -- Mark Twain
.



Relevant Pages

  • Re: Opinions on procedural language being introduced into SQL Server 2005
    ... integration, so no need to venture into the dark side of managed code << ... that is not the Standard SQL/PSM syntax and I am not sure ... the middle and exception handlers at the bottom. ... The key word is WHENEVER, ...
    (microsoft.public.sqlserver.programming)
  • Re: Access Integration Opportunities
    ... I have "integrated" (i.e. different level or scope of integration) Access ... -oil and gas forcast/engineering software, ... Naturally I was able to answer with the standard ... > Microsoft products such as VB, Excel, Outlook, and Powerpoint, but that ...
    (microsoft.public.access.externaldata)
  • Re: what werent structure/union/map made part of F77/90 ?
    ... > standard for how many places something gets said about derived types. ... > integration, intended only to standardize old codes, then that would not ... Visual Fortran compiler. ... Kinda hard to track them all down and eliminate them with limited staff. ...
    (comp.lang.fortran)
  • Re: Fitting of Data
    ... Standard 2-D magnetostatic problem. ... There is an advantage as the coefficients are independent (as you ... the coefficients are produced by integration ... so, strictly speaking, continuous data is assumed. ...
    (sci.physics)
  • Re: Is it possible to invoke a Unix command within Fortran 90 source
    ... response: the program is not conformant with the Fortran standard. ...
    (comp.lang.fortran)