public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jarrydb at cse dot unsw.edu.au" <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:34:00 -0000	[thread overview]
Message-ID: <bug-49399-4-2E7vrWR0jZ@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 #7 from Jarryd Beck <jarrydb at cse dot unsw.edu.au> 2011-06-14 12:34:35 UTC ---
(In reply to comment #6)
> (In reply to comment #4)
> > Ah, I see. Well the example you gave also doesn't compile. This is exactly what
> > the boost library does too, I missed that part in their code, meaning that
> > parts of boost no longer compile with gcc 4.7.
> 
> And I know it doesn't, as I said "G++ doesn't accept it because access checking
> is not done as part of the substitution process yet."
> 
> Even when that's done, it will only be valid C++0x not, C++03.

Ok, I thought that was what you meant. Does this however mean that this bug is
now valid for C++0x, given what they say in the link that you gave?

"If a substitution results in an invalid type or expression, type deduction
fails. An invalid type or expression is one that would be ill-formed if written
using the substituted arguments. [Note: Access checking is not done as part of
the substitution process. —end note]"

Should a bug for the reverse also be filed for the C++03 part of gcc? I wonder
what boost mpl people would say about a bug report since this actually works
even though it's wrong...


  parent reply	other threads:[~2011-06-14 12:34 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 [this message]
2011-06-14 12:35 ` jarrydb at cse dot unsw.edu.au
2011-06-14 12:41 ` redi at gcc dot gnu.org
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-2E7vrWR0jZ@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).