public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iguchi at coral dot t dot u-tokyo dot ac dot jp" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/25135] New: Interface name does not conflict with subroutine name Date: Mon, 28 Nov 2005 12:22:00 -0000 [thread overview] Message-ID: <bug-25135-9795@http.gcc.gnu.org/bugzilla/> (raw) The following program should occur an error since the same named entity from different modules cannot be referenced. However, I compiled successfully, and got output "foo". I think it is wrong behavior. module m_foo contains subroutine foo print *, "foo" end subroutine end module module m_bar interface foo module procedure bar end interface contains subroutine bar print *, "bar" end subroutine end module use m_foo use m_bar call foo end -- Summary: Interface name does not conflict with subroutine name Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: iguchi at coral dot t dot u-tokyo dot ac dot jp http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25135
next reply other threads:[~2005-11-28 12:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-28 12:22 iguchi at coral dot t dot u-tokyo dot ac dot jp [this message] 2005-11-28 13:19 ` [Bug fortran/25135] " pinskia at gcc dot gnu dot org 2006-12-27 13:47 ` pault at gcc dot gnu dot org 2007-01-01 20:47 ` [Bug fortran/25135] [4.2 and 4.1 only] " pault at gcc dot gnu dot org 2007-01-06 14:14 ` pault at gcc dot gnu dot org 2007-01-06 14:17 ` [Bug fortran/25135] [4.1 " pault at gcc dot gnu dot org 2007-01-10 19:12 ` pinskia 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-25135-9795@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).