public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/6709] typeof() cannot be used with the :: operator
Date: Mon, 08 Mar 2010 14:40:00 -0000 [thread overview]
Message-ID: <20100308144033.25580.qmail@sourceware.org> (raw)
In-Reply-To: <bug-6709-3116@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from redi at gcc dot gnu dot org 2010-03-08 14:40 -------
(In reply to comment #8)
> Hmm, I wonder what the current draft of C++0x says of decltype with this
> respect (right now we reject it).
>
In Bug 43285 Comment 1 I said that I think decltype is invalid in this context,
which would make this a documentation bug for C++.
In the C++0x grammar:
simple-type-specifier:
::_opt nested-name-specifier_opt type-name
...
decltype ( expression )
nested-name-specifier:
type-name ::
namespace-name ::
nested-name-specifier identifier ::
nested-name-specifier template_opt simple-template-id ::
type-name:
class-name
enum-name
typedef-name
So decltype(expression) cannot appear in a nested-name-specifier
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6709
next prev parent reply other threads:[~2010-03-08 14:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6709-3116@http.gcc.gnu.org/bugzilla/>
2007-02-17 20:02 ` pinskia at gcc dot gnu dot org
2007-08-12 2:05 ` pinskia at gcc dot gnu dot org
2010-03-08 14:29 ` bangerth at gmail dot com
2010-03-08 14:40 ` redi at gcc dot gnu dot org [this message]
2010-03-08 14:46 ` redi at gcc dot gnu dot org
2010-03-08 16:00 ` manu at gcc dot gnu dot org
2010-03-08 16:10 ` [Bug c++/6709] [DR743] " redi at gcc dot gnu dot org
2010-04-18 6:48 ` [Bug c++/6709] [DR743] decltype " pinskia at gcc dot gnu dot org
2010-04-18 12:56 ` faisalv at yahoo dot com
2010-04-19 9:38 ` redi at gcc dot gnu dot org
[not found] <20020517154601.6709.marco@technoboredom.net>
2003-09-23 21:08 ` [Bug c++/6709] typeof() " pinskia at gcc dot gnu dot org
2003-11-24 23:05 ` hakonrk at fys dot uio dot no
2004-02-13 5:39 ` pinskia at gcc dot gnu dot org
2005-03-19 13:48 ` pinskia 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=20100308144033.25580.qmail@sourceware.org \
--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).