public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "florent dot gallet at orange dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/21783] New: No typedef required when type use in a function
Date: Fri, 27 May 2005 14:40:00 -0000	[thread overview]
Message-ID: <20050527143655.21783.florent.gallet@orange.fr> (raw)

template<class T> struct A {
  typedef int B;
  void f(typename A::B);    // illformed: typename required before A::B 
  A::B b;          // ok error detected
};

It's in the DRAFT: 25 November 1997
14.6 Name resolution

I don't know if that changed.
If someone could confirm.

-- 
           Summary: No typedef required when type use in a function
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: florent dot gallet at orange dot fr
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2005-05-27 14:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27 14:40 florent dot gallet at orange dot fr [this message]
2005-05-27 14:42 ` [Bug c++/21783] No typename " florent dot gallet at orange dot fr
2005-05-27 14:43 ` florent dot gallet at orange dot fr
2005-05-27 14:48 ` pinskia at gcc dot gnu dot org
2005-05-27 15:02 ` florent dot gallet at orange dot fr
2005-05-27 15:25 ` florent dot gallet at orange dot fr
2005-05-27 15:50 ` florent dot gallet at orange dot fr
2005-06-07 17:07 ` reichelt at gcc dot gnu dot org
2005-06-07 18:45 ` giovannibajo at libero dot it
2005-06-07 19:07 ` [Bug c++/21783] [DR 409] Typename for required for qualified name? reichelt 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=20050527143655.21783.florent.gallet@orange.fr \
    --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).