public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: Gabriel Dos Reis <gdr@integrable-solutions.net>
Cc: Andrew Cagney <ac131313@redhat.com>,
	Nathanael Nerode <neroden@twcny.rr.com>,
	fche@redhat.com, gdb@sources.redhat.com,
	binutils@sources.redhat.com, hjl@lucon.org
Subject: Re: FYI: A new C++ demangler
Date: Tue, 15 Jul 2003 19:16:00 -0000	[thread overview]
Message-ID: <m3n0ffmwi0.fsf@gossamer.airs.com> (raw)
In-Reply-To: <m3vfu3aczu.fsf@uniton.integrable-solutions.net>

Gabriel Dos Reis <gdr@integrable-solutions.net> writes:

> Nathanael Nerode <neroden@twcny.rr.com> wrote
> | > We *don't* want to add such a build requirement for GCC or binutils,
> | > for very good reasons (a lot of systems don't ship with a C++
> | > compiler).  HJ keeps proposing a *completely* demented idea, which
> | > is that the new demangler will be used if a C++ compiler happens to
> | > be lying around during build, and otherwise the broken demangler
> | > will be used.  I wish he'd see what's wrong with that picture.
> 
> I think the completely  demented idea is insisting that "lot of
> systems don't ship with a C++ compiler" and continuing to demande to
> continue a broken implementation. 

But the GNU binutils are intended to be widely portable, and on some
systems the GNU binutils are required in order to build g++, and some
systems really don't ship with a C++ compiler.

If we want to rewrite the GNU binutils in C++, that would be a
reasonable discussion, and in fact C++ would bring a number of
advantages.  But it makes no sense to try to sneak a C++ requirement
in by the back door.

Also, who exactly is demanding to continue a broken implementation?
It really can not be all that difficult to fix the current demangler.

Ian

  parent reply	other threads:[~2003-07-15 19:16 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-12 18:02 Nathanael Nerode
2003-07-15 16:17 ` Andrew Cagney
2003-07-15 18:03   ` Gabriel Dos Reis
2003-07-15 19:02     ` Andrew Cagney
2003-07-15 19:03     ` Alexandre Oliva
2003-07-15 19:16       ` H. J. Lu
2003-07-15 19:49         ` Alexandre Oliva
2003-07-15 19:55           ` H. J. Lu
2003-07-15 22:30             ` Alexandre Oliva
2003-07-15 23:14               ` H. J. Lu
2003-07-16  2:31                 ` Alexandre Oliva
2003-07-16  3:21                 ` Ian Lance Taylor
2003-07-16 17:12       ` Nathanael Nerode
2003-07-15 19:16     ` Ian Lance Taylor [this message]
2003-07-15 19:23       ` H. J. Lu
2003-07-15 20:05       ` DJ Delorie
  -- strict thread matches above, loose matches on Subject: below --
2003-07-11  0:36 Michael Elizabeth Chastain
2003-07-10 21:57 Michael Elizabeth Chastain
2003-07-10 15:42 Michael Elizabeth Chastain
2003-07-10 15:51 ` H. J. Lu
2003-07-10 16:38 ` Ian Lance Taylor
2003-07-10 14:36 H. J. Lu
2003-07-10 14:40 ` Ian Lance Taylor
2003-07-10 14:54   ` H. J. Lu
2003-07-10 15:28 ` David Carlton
2003-07-10 15:36   ` H. J. Lu
2003-07-10 15:44     ` David Carlton
2003-07-10 20:57 ` Mark Kettenis
2003-07-10 21:17   ` Andrew Cagney
2003-07-10 21:44     ` H. J. Lu
2003-07-10 22:58     ` Frank Ch. Eigler
2003-07-10 23:19       ` Andrew Cagney
2003-07-10 21:22   ` DJ Delorie

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=m3n0ffmwi0.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=fche@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=gdr@integrable-solutions.net \
    --cc=hjl@lucon.org \
    --cc=neroden@twcny.rr.com \
    /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).