public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19073] cp_binding_level::names not returning all decls
Date: Mon, 20 Dec 2004 03:53:00 -0000 [thread overview]
Message-ID: <20041220035342.28474.qmail@sourceware.org> (raw)
In-Reply-To: <20041219004116.19073.sstrasser@systemhaus-gruppe.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-20 03:53 -------
(In reply to comment #7)
> I understand what they're doing but I don't understand why they are at this
> point and were introduced in decl.c version 1.1114.
> the cvs log message doesn't contain anything that's useful to me either.
> why are these lines there? before this there was no assignment to binding->value
> at all.
http://gcc.gnu.org/ml/gcc-patches/2003-08/msg01155.html
" The bug report had to do with allowing invalid elaborated type
specifiers. The root cause was that we were treating
namespace-scope bindings differently from local and class bindings;
this patch makes things more uniform."
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19073
next prev parent reply other threads:[~2004-12-20 3:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 0:41 [Bug c++/19073] New: cp_namespace_decl " sstrasser at systemhaus-gruppe dot de
2004-12-19 0:52 ` [Bug c++/19073] " pinskia at gcc dot gnu dot org
2004-12-19 0:53 ` pinskia at gcc dot gnu dot org
2004-12-19 1:04 ` sstrasser at systemhaus-gruppe dot de
2004-12-19 1:15 ` pinskia at gcc dot gnu dot org
2004-12-19 3:35 ` [Bug c++/19073] cp_binding_level::names " sstrasser at systemhaus-gruppe dot de
2004-12-19 3:47 ` sstrasser at systemhaus-gruppe dot de
2004-12-19 3:47 ` [Bug c++/19073] cp_binding_level sstrasser at systemhaus-gruppe dot de
2004-12-19 15:32 ` [Bug c++/19073] cp_binding_level::names not returning all decls gdr at integrable-solutions dot net
2004-12-19 16:10 ` pcarlini at suse dot de
2004-12-20 3:42 ` sstrasser at systemhaus-gruppe dot de
2004-12-20 3:53 ` pinskia at gcc dot gnu dot org [this message]
2005-05-15 11:46 ` lerdsuwa at gcc dot gnu dot org
2005-05-15 16:21 ` sstrasser at systemhaus-gruppe dot de
2005-05-15 16:47 ` gdr at integrable-solutions dot net
[not found] <bug-19073-4@http.gcc.gnu.org/bugzilla/>
2024-02-16 18:02 ` mpolacek 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=20041220035342.28474.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).