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/49591] [OOP] Multiple identical specific procedures in type-bound operator not detected
Date: Thu, 04 Aug 2011 19:40:00 -0000	[thread overview]
Message-ID: <bug-49591-4-rVQddUMR6q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49591-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49591

--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-08-04 19:39:32 UTC ---
(In reply to comment #1)
> Adjusting title. The problem really only applies to (type-bound) *operators*,
> right?

No idea. The example is, but I don't know whether other generics are properly
checked for ambiguity or not.


  parent reply	other threads:[~2011-08-04 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 12:53 [Bug fortran/49591] New: [OOP] Multiple identical specific procedures in type-bound generic " burnus at gcc dot gnu.org
2011-08-04 16:50 ` [Bug fortran/49591] [OOP] Multiple identical specific procedures in type-bound operator " janus at gcc dot gnu.org
2011-08-04 19:36 ` burnus at gcc dot gnu.org
2011-08-04 19:40 ` burnus at gcc dot gnu.org [this message]
2011-08-04 20:06 ` janus at gcc dot gnu.org
2012-06-25 19:06 ` janus at gcc dot gnu.org
2012-06-27 17:38 ` janus at gcc dot gnu.org
2012-06-27 17:51 ` janus 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-49591-4-rVQddUMR6q@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).