public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eh.toussaint at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49265] Double colon in procedure-stmt (generic interface)
Date: Fri, 13 Jul 2012 22:30:00 -0000 [thread overview]
Message-ID: <bug-49265-4-fdAwa1GPna@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49265-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49265
Erik Toussaint <eh.toussaint at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |
--- Comment #5 from Erik Toussaint <eh.toussaint at gmail dot com> 2012-07-13 22:30:24 UTC ---
Sorry to reopen this after more than a year.
I think the following syntax, without the 'module' prefix, is also supposed to
be ok, but it's currently not accepted (gfortran 4.7.0), with the same error
message as in the original report.
procedure :: bar
1
Error: Syntax error in PROCEDURE statement at (1)
next prev parent reply other threads:[~2012-07-13 22:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 23:28 [Bug fortran/49265] New: " eh.toussaint at gmail dot com
2011-06-02 0:27 ` [Bug fortran/49265] " kargl at gcc dot gnu.org
2011-06-02 17:40 ` kargl at gcc dot gnu.org
2011-06-02 19:53 ` kargl at gcc dot gnu.org
2011-06-02 19:55 ` kargl at gcc dot gnu.org
2012-07-13 22:30 ` eh.toussaint at gmail dot com [this message]
2012-07-14 11:21 ` burnus at gcc dot gnu.org
2012-07-17 8:59 ` burnus at gcc dot gnu.org
2012-07-17 9:00 ` burnus at gcc dot gnu.org
2012-07-17 9:01 ` burnus 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=bug-49265-4-fdAwa1GPna@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).