Re: generic interface real function vs real

It compiles and runs perfectly with GNU Fortran (GCC) 4.2.3, but ifort
(IFORT) 10.0 20070426 complains

I was going to say that this is an Intel bug, because it looked OK to me
and other compilers certainly did accept it (Sun, gfortran, IBM) but
Lahey also complains. So, I looked into the F2003 standard and I think
that's what the last example (INTERFACE BAD9) of C.11.2 says: it is
unambiguous, but still invalid, because: "the rules do not distinguish on
the basis of any properties other than type, kind type parameters, and
rank".

Anyone willing to confirm/infirm this?

PS: the root cause for that might be the will to have some simpler rules,
but it is a bit sad if the example showed by the poster is invalid
(moreover, these rules *are* complex anyway).

--
FX
.

Relevant Pages

  • Re: generic interface real function vs real
    ... and other compilers certainly did accept it but ... Lahey also complains. ... the basis of any properties other than type, kind type parameters, and ... KIND types available in the g95 compiler (at the time of writing quad ...
    (comp.lang.fortran)
  • Invalid cast when trying to reference a database column...
    ... theField = reader.GetString; ... the first line is crashing my program. ... it complains about an invalid ...
    (microsoft.public.dotnet.languages.csharp)
  • counter.li.org madness
    ... my machine-update script from there complains about a ... "Invalid or incomplete multibyte or wide character" when started with -m to ...
    (alt.os.linux)
  • Re: alpine, gpg and non-ascii chars
    ... using claws (which complains that the signature is invalid). ... If I use non-us characters and DON'T sign the mail. ...
    (comp.mail.pine)
  • Re: gfortran -std=f95 overzealous?
    ... gfortran complains that their use here is an extension to the ... Fortran-95 standard. ... None of my other compilers complain (with f95 ... by gfortran which just complains with - ...
    (comp.lang.fortran)