public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49399] [C++0x] substitution failure error
Date: Tue, 14 Jun 2011 12:41:00 -0000	[thread overview]
Message-ID: <bug-49399-4-KS4Znu99jA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49399-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-06-14 12:40:52 UTC ---
Note that returning 4 was *never* correct for that program.  In C++03 it
shouldn't compile and in C++0x it should return 1.  There's a bug in the
Boost.MPL docs which should say the macro works for *public* nested type member
x::name and cannot be used if the name is not accessible (and if you report
that you might as well also report the docs keep saying "memeber")

There are already several bug reports for G++ not doing access checking
correctly in templates, no need to report another one.  You could consider it a
bug that the resolution of DR1170 isn't implemented yet, but it's a known
missing feature that simply hasn't been implemented yet.


  parent reply	other threads:[~2011-06-14 12:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14  7:12 [Bug c++/49399] New: " jarrydb at cse dot unsw.edu.au
2011-06-14  8:15 ` [Bug c++/49399] " redi at gcc dot gnu.org
2011-06-14 11:53 ` jarrydb at cse dot unsw.edu.au
2011-06-14 12:11 ` redi at gcc dot gnu.org
2011-06-14 12:22 ` jarrydb at cse dot unsw.edu.au
2011-06-14 12:28 ` redi at gcc dot gnu.org
2011-06-14 12:31 ` redi at gcc dot gnu.org
2011-06-14 12:34 ` jarrydb at cse dot unsw.edu.au
2011-06-14 12:35 ` jarrydb at cse dot unsw.edu.au
2011-06-14 12:41 ` redi at gcc dot gnu.org [this message]
2011-06-15 16:47 ` jason 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-49399-4-KS4Znu99jA@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).