From: Andrew Cagney <ac131313@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Andrew Cagney <cagney@redhat.com>,
Mark Kettenis <kettenis@chello.nl>, "H. J. Lu" <hjl@lucon.org>,
binutils@sources.redhat.com, GDB <gdb@sources.redhat.com>
Subject: Re: FYI: A new C++ demangler
Date: Thu, 10 Jul 2003 23:19:00 -0000 [thread overview]
Message-ID: <3F0DF491.6030605@redhat.com> (raw)
In-Reply-To: <o5znjmhtuz.fsf@toenail.toronto.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
> cagney wrote:
>
>
>> [...]
>
>> > Could someone fix the old demangler, or write a new one in
>> > plain C (or re-write the C++ one in C)? Pretty please?
>
>>
>> Yes. There's no reason for the underlying demangler algorithm to be
>> implemented in vanila ISO C 90, and then wrap it for the C++ side.
>> [...]
>
>
> You might be accused of dogmatic monolingualism if you don't accept
> the notion that some such code may be more naturally expressed in a
> higher level language -- that could be one such reason. Another
> reason of course is the fact that it is already done and working:
> rewriting costs new effort.
High level language? I guess that rules out C++ then :-)
> (Note that I'm not asserting that the former reason applies strongly
> here; libstdc++-v3/include/bits/demangle.h for example doesn't seem to
> rely much on the C++ language's extra capabilities.)
That was my, and I'm guessing Marks, point.
Andrew
[-- Attachment #2: mailbox-message://ac131313@movemail/fsf/gdb/misc#1138377 --]
[-- Type: message/rfc822, Size: 2991 bytes --]
From: fche@redhat.com (Frank Ch. Eigler)
To: Andrew Cagney <cagney@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, "H. J. Lu" <hjl@lucon.org>, binutils@sources.redhat.com, GDB <gdb@sources.redhat.com>
Subject: Re: FYI: A new C++ demangler
Date: 10 Jul 2003 18:58:28 -0400
Message-ID: <o5znjmhtuz.fsf@toenail.toronto.redhat.com>
cagney wrote:
> [...]
> > Could someone fix the old demangler, or write a new one in
> > plain C (or re-write the C++ one in C)? Pretty please?
>
> Yes. There's no reason for the underlying demangler algorithm to be
> implemented in vanila ISO C 90, and then wrap it for the C++ side.
> [...]
You might be accused of dogmatic monolingualism if you don't accept
the notion that some such code may be more naturally expressed in a
higher level language -- that could be one such reason. Another
reason of course is the fact that it is already done and working:
rewriting costs new effort.
(Note that I'm not asserting that the former reason applies strongly
here; libstdc++-v3/include/bits/demangle.h for example doesn't seem to
rely much on the C++ language's extra capabilities.)
- FChE
next prev parent reply other threads:[~2003-07-10 23:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2003-07-10 21:22 ` DJ Delorie
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 21:57 Michael Elizabeth Chastain
2003-07-11 0:36 Michael Elizabeth Chastain
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
2003-07-15 19:23 ` H. J. Lu
2003-07-15 20:05 ` 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=3F0DF491.6030605@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=cagney@redhat.com \
--cc=fche@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=kettenis@chello.nl \
/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