public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/16848] code in /ext/demangle.h appears broken
Date: Mon, 02 Aug 2004 13:26:00 -0000 [thread overview]
Message-ID: <20040802132608.10797.qmail@sourceware.org> (raw)
In-Reply-To: <20040801025152.16848.igodard@pacbell.net>
------- Additional Comments From bangerth at dealii dot org 2004-08-02 13:26 -------
libstdc++ people:
I guess you have to make up your mind: Ivan's request for clarification
and changes to enhance usability are definitely valid. You can't tell
him in one PR that the one demangler isn't what he wants to use and
point him to the other one, and then with the other one tell him that
this is actually not for public use and therefore not optimized for
usability. That just doesn't go very well with users.
I think his requests to
- give the allocator a default argument
- remove references to internals from the public interface
- allow code to be compiled
are valid indeed. Please consider alternatives beyond "this is how it is
intended".
W.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16848
next prev parent reply other threads:[~2004-08-02 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-01 2:51 [Bug libstdc++/16848] New: " igodard at pacbell dot net
2004-08-01 2:54 ` [Bug libstdc++/16848] " igodard at pacbell dot net
2004-08-01 18:44 ` pcarlini at suse dot de
2004-08-01 20:13 ` carlo at gcc dot gnu dot org
2004-08-01 21:02 ` igodard at pacbell dot net
2004-08-02 13:26 ` bangerth at dealii dot org [this message]
2004-08-02 13:43 ` pcarlini at suse dot de
2004-09-02 16:56 ` cvs-commit at gcc dot gnu dot org
2004-09-23 18:20 ` pinskia at gcc dot gnu dot org
2004-09-27 17:26 ` cvs-commit at gcc dot gnu dot org
2004-09-27 17:28 ` 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=20040802132608.10797.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).