public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3033: 'using typename' construct doesn't work
Date: Fri, 01 Jun 2001 18:46:00 -0000 [thread overview]
Message-ID: <20010602014603.31191.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/3033; it has been noted by GNATS.
From: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>
To: sethml@ofb.net
Cc: Gabriel Dos Reis <Gabriel.Dos-Reis@cmla.ens-cachan.fr>,
gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: Re: c++/3033: 'using typename' construct doesn't work
Date: 02 Jun 2001 03:44:10 +0200
sethml@ofb.net writes:
| > sethml@ofb.net writes:
| >
| > | C++ allows the word 'typename' after a 'using' directive. _The C++ Pro
| > gramming Language_ (third edition) [Stroustrup], section A.7 (Grammar/Declara
| > tions) defines the using directive:
| > | using-declaration:
| > | "using" "typename"(opt) "::"(opt) nested-name-specifier
| > | unqualified-id ";"
| >
| > The C++ grammar is not context-free, you cannot deduce construct
| > validity just from pure grammar productions.
|
| OK, fine. The question remains: is this a legal construct, or not?
The constructs you sent were all ill-formed. See 14.6/5 of the C++
definition text.
-- Gaby
next reply other threads:[~2001-06-01 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-01 18:46 Gabriel Dos Reis [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-01 19:36 Jonathan Adamczewski
2001-06-01 18:26 sethml
2001-06-01 18:06 Gabriel Dos Reis
2001-06-01 13:46 sethml
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=20010602014603.31191.qmail@sourceware.cygnus.com \
--to=gabriel.dos-reis@cmla.ens-cachan.fr \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).