------- Comment #7 from toon at moene dot indiv dot nluug dot nl 2008-02-15
18:15 -------
> As written, I checked all my compilers and all get a wrong result
> - gfortran, g95, NAG f95: NOT PRESENT
> - ifort: PRESENT, WITH VALUE: 0 (even if not present)
> (ifort 10 and ifort 10.1 print a warning that present should not be used
> with
> value; ifort 9 give the same run-time result, but does not have the warning)
> - sunf95: Compile-time error: OPTIONAL and VALUE may not be used both
I just asked Bill Long of Cray (who heads the subgroup that covers this) to try
it on Cray's compiler - it ICE'd with a message that clearly showed that it
didn't expect to be handed an OPTIONAL, VALUE argument (without flagging it as
a not-legal construct, though).
I'm closing the PR as "WONTFIX".
> (While we are at it: Please make sure that OPTION + VALUE + BIND(C) will not
> be
> allowed in the upcoming interoperability TR; if it is included, there should
> be
> a note giving implementation suggestions. F2003 is unaffected by this as
> OPTIONAL is not allowed with BIND(C).)
You bet. There was a heated discussion on this yesterday, which didn't result
in any progress. Bill will send out an e-mail with the issues.
--
toon at moene dot indiv dot nluug dot nl changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35203
