From: Daniel Jacobowitz <drow@false.org>
To: "Thomas Kühne" <thomas@kuehne.cn>, "Jim Blandy" <jimb@red-bean.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: D Symbol Demangling
Date: Mon, 24 Apr 2006 20:53:00 -0000 [thread overview]
Message-ID: <20060424205328.GB27220@nevyn.them.org> (raw)
In-Reply-To: <8f2776cb0604241021xbf7e2djca7cd6a25057d8a3@mail.gmail.com> <44495B98.7010407@kuehne.cn>
On Mon, Apr 24, 2006 at 10:21:15AM -0700, Jim Blandy wrote:
> The other demanglers are all in libiberty; shouldn't this one go there, too?
Well, the old and new C++ demanglers are in libiberty, and the "Java
demangler" is part of that. But there's an Ada demangler in GDB
already.
On Sat, Apr 22, 2006 at 12:24:24AM +0200, Thomas Kühne wrote:
> I've no problem with assigning the copyright of the demangler to the FSF if
> the license issue - as you noted, using more than one license might cause
> problems - can be solved.
>
> The GPL with linking exception would seem to be the best solution for all.
> (taken from /usr/portage/licenses/GPL-2-with-linking-exception)
>
> | As a special exception, the copyright holders of this library give you
> | permission to link this library with independent modules to produce an
> | executable, regardless of the license terms of these independent modules,
> | and to copy and distribute the resulting executable under terms of your
> | choice, provided that you also meet, for each linked independent module,
> | the terms and conditions of the license of that module. An independent
> | module is a module which is not derived from or based on this library. If
> | you modify this library, you may extend this exception to your version of
> | the library, but you are not obligated to do so. If you do not wish to do
> | so, delete this exception statement from your version.
>
> <followed by the GPL text>
I don't know what permissions we need to generate new code under this
license; does anyone else know? Do we need to check it with the FSF?
They're usually reasonable about such things, but obviously they prefer
the stronger GPL when possible.
> > And, no offense, but the DD_() thing is horribly ugly and doesn't seem
> > to serve any purpose here. Is that for reusing the demangler
> > elsewhere?
>
> Yes it's ugly and not the kind of code I normally write.
> The problem: the demangler is currently used with GDB, Valgrind and 3
> in-house tools - thus name and symbol clashes are a real problem.
What's the actual interface to the demangler? All I see is a single
function:
char* DD_(demangle_d)(char*);
If that's the case, it ought to be possible to make everything else
static by careful use of #include, and then presto - no name clashes.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-04-24 20:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 11:18 Thomas Kuehne
2006-04-20 13:20 ` Daniel Jacobowitz
2006-04-20 15:20 ` OT: copyright issues (was: Re: D Symbol Demangling) Baurzhan Ismagulov
2006-04-20 15:40 ` DJ Delorie
2006-04-20 15:46 ` Daniel Jacobowitz
2006-04-20 16:39 ` Baurzhan Ismagulov
2006-04-20 17:05 ` Daniel Jacobowitz
2006-04-20 17:11 ` Baurzhan Ismagulov
2006-04-21 21:25 ` D Symbol Demangling Thomas Kühne
2006-04-22 22:52 ` Thomas Kühne
2006-04-24 17:21 ` Jim Blandy
2006-04-24 20:53 ` Daniel Jacobowitz [this message]
2006-04-25 3:35 ` Eli Zaretskii
2006-04-25 14:13 ` DJ Delorie
2006-04-29 7:23 ` Thomas Kühne
2006-04-29 16:47 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 2:37 John Demme
2005-04-04 18:21 ` Michael Snyder
2005-04-04 20:44 ` John Demme
2005-04-04 20:47 ` Daniel Jacobowitz
2005-04-04 21:49 ` Michael Snyder
2005-04-04 22:39 ` John Demme
[not found] ` <1112654359.14153.50.camel@localhost.localdomain>
[not found] ` <4251CF00.5080002@redhat.com>
2005-04-08 16:47 ` John Demme
2005-04-08 16:52 ` Daniel Jacobowitz
2005-04-08 20:50 ` John Demme
2005-04-08 21:11 ` Daniel Jacobowitz
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=20060424205328.GB27220@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@red-bean.com \
--cc=thomas@kuehne.cn \
/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