public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "akim.demaille at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53540] New: C++11: using fails to be equivalent to typedef
Date: Thu, 31 May 2012 14:44:00 -0000	[thread overview]
Message-ID: <bug-53540-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 53540
           Summary: C++11: using fails to be equivalent to typedef
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: akim.demaille@gmail.com


Created attachment 27532
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27532
test case

Hi all,

I hope this is not a bogus bug report, I apologize if there is something I
misunderstood.  I observed the following with both 4.7.0 and "4.8":

g++-mp-4.7 (MacPorts gcc47 4.7.0_3) 4.7.0
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

g++-mp-4.8 (MacPorts gcc48 4.8-20120527_1) 4.8.0 20120527 (experimental)
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

In the following example, I import a type name from a templates struct with
"using", and do the same with "typedef".  The latter works, but "using" does
not seem to find the definition.  clang finds it though (but then again, my
understanding might be wrong).

If "function" is not templated, there is no problem.


$ cat foo.cc
template <typename T>
struct context
{
  typedef int type;
};

template <typename T>
void function()
{
  using ctx1 = context<T>;
  typename ctx1::type f1;

  typedef context<T> ctx2;
  typename ctx2::type f2;
}

int main()
{
  function<int>();
}


$ g++-mp-4.8 -Wall -std=c++11 foo.cc
foo.cc: In instantiation of 'void function() [with T = int]':
foo.cc:19:17:   required from here
foo.cc:11:23: error: no type named 'type' in 'using ctx1 = struct context<T>'
   typename ctx1::type f1;
                       ^
foo.cc:14:23: warning: unused variable 'f2' [-Wunused-variable]
   typename ctx2::type f2;
                       ^


             reply	other threads:[~2012-05-31 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 14:44 akim.demaille at gmail dot com [this message]
2012-05-31 17:43 ` [Bug c++/53540] " redi at gcc dot gnu.org
2012-06-11 17:27 ` akim.demaille at gmail dot com
2012-08-16 19:09 ` dodji at gcc dot gnu.org
2012-08-16 19:11 ` dodji at seketeli dot org
2012-08-16 22:18 ` dodji at seketeli dot org
2012-10-05 21:29 ` paolo.carlini at oracle dot com
2012-10-08 14:27 ` dodji at seketeli dot org
2012-10-10 10:44 ` dodji at gcc dot gnu.org
2012-10-10 10:57 ` dodji at gcc dot gnu.org
2013-05-03  9:54 ` paolo.carlini at oracle dot com

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-53540-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: 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).