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/52295] New: Allow internal procedure in generic interfaces Date: Fri, 17 Feb 2012 11:56:00 -0000 [thread overview] Message-ID: <bug-52295-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52295 Bug #: 52295 Summary: Allow internal procedure in generic interfaces Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Keywords: diagnostic, patch, rejects-valid Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned@gcc.gnu.org ReportedBy: burnus@gcc.gnu.org Found at http://groups.google.com/group/comp.lang.fortran/browse_thread/thread/408949dd41f76a86 gfortran rejects internal procedures in generic interfaces with -std=2008, but that's valid since F2008. Fortran 2003: C1207 (R1206) A procedure-name shall have an explicit interface and shall refer to an accessible procedure pointer, external procedure, dummy procedure, or module procedure. Fortran 2008: C1207 (R1206) A procedure-name shall be a nonintrinsic procedure that has an explicit interface. Untested patch: --- interface.c (revision 184331) +++ interface.c (working copy) @@ -1292,9 +1292,10 @@ return 1; } + /* F2003, C1207. F2008, C1207. */ if (p->sym->attr.proc == PROC_INTERNAL - && gfc_notify_std (GFC_STD_GNU, "Extension: Internal procedure '%s' " - "in %s at %L", p->sym->name, interface_name, + && gfc_notify_std (GFC_STD_F2008, "Fortran 2008: Internal procedure " + "'%s' in %s at %L", p->sym->name, interface_name, &p->sym->declared_at) == FAILURE) return 1; }
next reply other threads:[~2012-02-17 11:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-17 11:56 burnus at gcc dot gnu.org [this message] 2012-02-18 12:32 ` [Bug fortran/52295] " burnus at gcc dot gnu.org 2012-02-18 12:37 ` 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-52295-4@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).