Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Thomas Kühne" <thomas@kuehne.cn>
To: gdb-patches@sources.redhat.com
Subject: Re: D Symbol Demangling
Date: Fri, 21 Apr 2006 21:25:00 -0000	[thread overview]
Message-ID: <44495B98.7010407@kuehne.cn> (raw)
In-Reply-To: <20060420132004.GB11710@nevyn.them.org>

Daniel Jacobowitz wrote:
> Unfortunately, there are several major problems with accepting this
> code.
> 
> 1.  Neither you nor John has an FSF copyright assignment in place.  If
> you're interested in one, let me know and I can send you the forms.
>
> 2.  The demangler would need to be contributed to the FSF and licensed
> under the GPL before we could include it with GDB.  That doesn't
> prevent another copy of it from being used under a different license
> elsewhere; but you wouldn't be able to import fixes from one to the
> other, in either direction.

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>

> 3.  The code would need to match the GNU Coding Standards.
> 
> 4.  A patch would need to be generated against HEAD, not against an old
> release.

working on that

> 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.

Thomas


  parent reply	other threads:[~2006-04-21 21:25 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   ` Thomas Kühne [this message]
2006-04-22 22:52     ` D Symbol Demangling Thomas Kühne
2006-04-24 17:21       ` Jim Blandy
2006-04-24 20:53         ` Daniel Jacobowitz
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=44495B98.7010407@kuehne.cn \
    --to=thomas@kuehne.cn \
    --cc=gdb-patches@sources.redhat.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