public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/41603] [-fwhole-file] Add diagnostic for assumed-length character function
Date: Tue, 06 Oct 2009 17:56:00 -0000 [thread overview]
Message-ID: <20091006175549.21154.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41603-13404@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from burnus at gcc dot gnu dot org 2009-10-06 17:55 -------
(In reply to comment #2)
> c) "If an explicit specific interface is specified by an interface body or a
> procedure declaration statement (12.3.2.3) for an external procedure, the
> characteristics shall be consistent with those specified in the procedure
> definition
Richard Main thinks that this disallows it:
'The special rule for assumed length says that this characteristic has to be
different, but this requirement says that the characteristic has to be
"consistent." I do wish that were defined better, but from context hints
I'd interpret "consistent" to mean "the same" for yes/no characteristics
like assumed character length. If one tried to interpret "consistent"
differently here, I'd wonder why that same interpretation wouldn't apply
to the purity matter cited as an exception.
'I suppose there is some ground for uncertainly here based on the
question of exactly how "consistent" is interpreted.'
I still do not quite see why it is allowed for implicit interfaces, but somehow
the following seems to allow it:
"If a type is specified for an external function, its function definition
(12.5.2.1) shall specify the same result type and type parameters."
(If it weren't allowed then one could not use it at all. And as it is a legacy
item, it must work without explicit interfaces which only exists since F90.)
Cf. http://groups.google.com/group/comp.lang.fortran/msg/3ea113a7b45471e5
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41603
next prev parent reply other threads:[~2009-10-06 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 14:26 [Bug fortran/41603] New: " burnus at gcc dot gnu dot org
2009-10-06 14:27 ` [Bug fortran/41603] " burnus at gcc dot gnu dot org
2009-10-06 14:57 ` burnus at gcc dot gnu dot org
2009-10-06 15:01 ` burnus at gcc dot gnu dot org
2009-10-06 17:56 ` burnus at gcc dot gnu dot org [this message]
2009-10-07 8:02 ` burnus at gcc dot gnu dot org
2009-10-14 16:10 ` burnus at gcc dot gnu dot org
[not found] <bug-41603-4@http.gcc.gnu.org/bugzilla/>
2011-03-13 15:54 ` pault at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091006175549.21154.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).