Re: Which version of Intel Fortran 1st had C Interop?



James Tursa <aclassyguywithaknotac@xxxxxxxxxxx> wrote:

Does anyone know which version of Intel Fortran was the first one to
have C interop capability?

I don't know the answer to your question, but I suspect that there are 2
different answers depending on exactly what you mean by the question.
Namely

1. If you mean C interop capability as a general term, I suspect that
goes back a long ways, perhaps to the first version.

2. You might mean specifically support of the f2003 ISO_C_BINDING
module, in which case, I still suspect there might be two different
answers depending on whether you mean the first version where they
included anything from that module or the first version where they fully
supported everything in it.

I wouldn't be shocked if full support of everything in it might still be
missing. After all, that module is an f2003 feature and it includes bits
that depend on other f2003 features. F2003 procedure pointers come to
mind. I don't recall whether Intel Fortran yet has f2003 procedure
pointers, but if it doesn't, then it can't very well be said to fully
support everything in the module.

This relates to my plaint in a thread a while back where I expressed
unhappiness with recent directions in Fortran standardization - in
particular the notion, expressed rather strongly by some (well at least
one, and I assume he isn't alone) proponents, that it is a collection of
features for vendors to pick from. I think that there are integration
matters that make it far harder to be sure of exactly what one is
talking about if one cites individual features instead of the whole
standard.

I can easily imagine an f95 vendor claiming to support the ISO_C_BINDING
module, but meaning only those parts of it that fit with the rest of his
compiler, which might be different from the impression that such a claim
might give to a user. Part of the reason that C interop was not done as
an f95 TR was that it didn't separate out cleanly enough as a standalone
feature; it has some clear standalone parts, but other things end up
interacting a bit much with the rest of the language. It was originally
proposed as am f95 TR, but that didn't work out (for several reasons,
but this was one).

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



Relevant Pages

  • SourceForge.net Sitewide update June 23rd, 2004 (fwd)
    ... Puzzle ITC provides software development services based on Open Source ... support of SourceForge.net. ... recent rolled out several other new features, ... lists. ...
    (comp.os.linux.announce)
  • Re: Embedded RTOS - features poll
    ... I currently have support for ARM9, ... Such an OS must help to developer with its ready features, ... linked lists in the RTOS. ... use native task manager API ...
    (comp.arch.embedded)
  • Re: B-Tree Index Usage
    ... Your support provider must apply pressure. ... in a public forum thanking you for your report. ... that many people don't use many of the "newer" features in D3 ... cared about "features" and pro-active vendors have moved on to vendors ...
    (comp.databases.pick)
  • Re: Linus 2.6.23-rc1
    ... # Processor type and features ... # PCCARD support ... # Device Drivers ... # USB Network Adapters ...
    (Linux-Kernel)
  • ANN: Dew Research releases support for Delphi 2007!
    ... trial version for Delphi 2007 and support for Delphi 2007 ... Other features include extensive set vectorized mathemathical ... MtxVec and thus taking advantage of its processing power. ...
    (borland.public.delphi.thirdpartytools.general)