public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/55895] multiple type-bound procedures Date: Mon, 07 Jan 2013 13:52:00 -0000 [thread overview] Message-ID: <bug-55895-4-OO1HN1GXWL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55895-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55895 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Last reconfirmed| |2013-01-07 CC| |burnus at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2013-01-07 13:51:52 UTC --- (In reply to comment #0) > Should gfortran complain with the following code I think it okay: procedure ::foo => afoo, bfoo is equivalent to: procedure :: foo => afoo procedure :: bfoo => bfoo >From Fortran 2008: R448 type-bound-procedure-stmt is PROCEDURE [ [ , binding-attr -list ] :: ] type-bound-proc-decl-list R449 type-bound-proc-decl is binding-name [ => procedure-name ] C464 (R448) If => procedure-name appears in a type-bound-proc-decl, the double-colon separator shall appear. If neither => procedure-name nor interface-name appears in a type-bound-proc-decl, it is as though => procedure-name had appeared with a procedure name the same as the binding name. Note: Fortran 2003 didn't allow a list, i.e. with -std=f2003 it is correctly rejected. Fortran 2003: R451 specific-binding is PROCEDURE [ (interface-name) ] [ [ , binding-attr -list ] :: ] binding-name [ => procedure-name ]
next prev parent reply other threads:[~2013-01-07 13:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-07 13:21 [Bug fortran/55895] New: " valeryweber at hotmail dot com 2013-01-07 13:52 ` burnus at gcc dot gnu.org [this message] 2013-06-17 15:24 ` [Bug fortran/55895] " dominiq at lps dot ens.fr
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-55895-4-OO1HN1GXWL@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: linkBe 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).