public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pault at gcc dot gnu.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: Sun, 13 Mar 2011 15:54:00 -0000 [thread overview]
Message-ID: <bug-41603-4-rZ7kt5sdiV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41603-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41603
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |pault at gcc dot gnu.org
Resolution| |WONTFIX
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> 2011-03-13 15:54:19 UTC ---
(In reply to comment #6)
> Just for completeness: The wording in
> J3/04-007 (p. 259, ll. 38-41; "12.3.2.1 Interface block")
> and in
> J3/97-007r2 (p. 194, ll. 32-34)
> is effectively the same. Thus there does not seem to be any change in the
> normative text. Assuming that there is none, I think concluding that the note
> still holds in F2003 is likely. I think I follow this line of thought and do
> not hand in an interpretation request.
>
> If someone does not think so, we can still do so - an IR is only little work
> for us and does also not take so much work in this case for J3/WG5.
Dear Tobias,
I think that this is a WONTFIX. Please reopen it if you disagree.
Cheers
Paul
next parent reply other threads:[~2011-03-13 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41603-4@http.gcc.gnu.org/bugzilla/>
2011-03-13 15:54 ` pault at gcc dot gnu.org [this message]
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
2009-10-07 8:02 ` burnus at gcc dot gnu dot org
2009-10-14 16:10 ` burnus at gcc dot gnu dot 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=bug-41603-4-rZ7kt5sdiV@http.gcc.gnu.org/bugzilla/ \
--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).