public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17743] dependent expressions in attributes
Date: Wed, 05 Oct 2005 21:16:00 -0000 [thread overview]
Message-ID: <20051005211632.1211.qmail@sourceware.org> (raw)
In-Reply-To: <bug-17743-365@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from rth at gcc dot gnu dot org 2005-10-05 21:16 -------
I'm surprised this is considered tricky. Seems to me you just stuff the
attribute away in the parse tree somewhere and pretend we've just read it
in during template instantiation. That's what we do with everything else
related to templates after all.
"A mere matter of programming", I'd think.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17743
next prev parent reply other threads:[~2005-10-05 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-17743-365@http.gcc.gnu.org/bugzilla/>
2005-10-05 21:03 ` bkoz at gcc dot gnu dot org
2005-10-05 21:06 ` bkoz at gcc dot gnu dot org
2005-10-05 21:16 ` rth at gcc dot gnu dot org [this message]
2005-10-05 22:34 ` mark at codesourcery dot com
2007-09-22 14:29 ` jason at gcc dot gnu dot org
2007-09-22 14:30 ` jason at gcc dot gnu dot org
2007-09-25 21:48 ` pinskia at gcc dot gnu dot org
2004-09-30 4:26 [Bug c++/17743] New: __alignof__ vs. typedefs bkoz at gcc dot gnu dot org
2004-10-17 4:48 ` [Bug c++/17743] dependent expressions in attributes giovannibajo at libero dot it
2004-10-17 7:50 ` gdr at cs dot tamu dot edu
2004-10-18 3:51 ` giovannibajo at libero dot it
2004-10-18 5:23 ` bkoz at redhat dot com
2004-10-18 16:38 ` giovannibajo at libero dot it
2004-10-18 18:57 ` bkoz at gcc dot gnu dot org
2004-10-19 6:23 ` bkoz at redhat dot com
2004-10-27 17:19 ` bkoz at gcc dot gnu dot org
2004-10-28 3:38 ` giovannibajo at libero dot it
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=20051005211632.1211.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).