public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10261: g++ does not error for bogus |typename| inside a templated class
Date: Mon, 07 Apr 2003 10:36:00 -0000	[thread overview]
Message-ID: <20030407103601.20199.qmail@sources.redhat.com> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]

The following reply was made to PR c++/10261; it has been noted by GNATS.

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<bbaetz@acm.org>
Cc:  
Subject: Re: c++/10261: g++ does not error for bogus |typename| inside a templated class
Date: Mon, 7 Apr 2003 12:27:45 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=10261
 
 Not a bug. §14.6p5:  "The keyword typename shall only be used in template
 declarations and definitions [...]  The keyword typename shall only be
 applied to qualified names, but those names need not be dependent."
 
 In other words, you cannot use 'typename' outside templates. You cannot use
 'typename' with unqualified names. You can use 'typename' for non-dependent
 qualified names (but it's not necessary). You must use 'typename' with
 dependent qualified names.
 
 Giovanni Bajo
 


             reply	other threads:[~2003-04-07 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 10:36 Giovanni Bajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-07 14:42 bangerth
2003-04-07 11:26 Bradley Baetz
2003-04-07 11:16 Giovanni Bajo
2003-04-07 10:56 Bradley Baetz
2003-03-29  8:34 Bradley Baetz
2003-03-29  2:36 bbaetz

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=20030407103601.20199.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --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).