This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New demangler bug and HOWTO-demangle (was Re: Demangle THIS)
- To: Carlo Wood <carlo at alinoe dot com>
- Subject: Re: New demangler bug and HOWTO-demangle (was Re: Demangle THIS)
- From: Tom Tromey <tromey at redhat dot com>
- Date: 04 Jul 2001 19:03:41 -0600
- Cc: Daniel Berlin <dan at cgsoftware dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- References: <20010621052336.A15429@alinoe.com> <87y9qlg8yc.fsf@cgsoftware.com> <20010704064739.A25505@alinoe.com> <87hewsmw7i.fsf@creche.redhat.com> <20010705013344.A9368@alinoe.com>
- Reply-To: tromey at redhat dot com
>>>>> "Carlo" == Carlo Wood <carlo@alinoe.com> writes:
Carlo> I have deliberately not looked at the source code of libiberty
Carlo> at all, so that nobody could accuse me of 'using' GPL-ed source
Carlo> for something that I wish to release under QPL (it sucks, but
Carlo> the main reason I reinvented the wheel and wrote my own
Carlo> demangler is the license).
FYI the demangler is LGPL, not GPL.
Carlo> I'll have a look at libiberties testsuite and see if I can come
Carlo> up with a test case.
I can't imagine how anyone could claim that using or reading the
libiberty demangler test suite would cause your program to violate the
GPL. If linking it in to your program was a requirement, then that
would be a problem. But I doubt you're interested in doing that.
Tom