This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC to open the C++ demangle API?
- From: Ross Smith <r-smith at ihug dot co dot nz>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 07 Mar 2002 18:10:47 +1300
- Subject: Re: GCC to open the C++ demangle API?
- Organization: No thanks
- References: <3C847E4E.AE15A0F3@ihug.co.nz> <8330000.1015451491@gandalf.codesourcery.com>
Mark Mitchell wrote:
>
> --On Tuesday, March 05, 2002 09:14:06 PM +1300 Ross Smith
> <r-smith@ihug.co.nz> wrote:
>
> > Zack Weinberg wrote:
> >>
> >> Dunno about Carlo's situation specifically, but there is a very real
> >> problem within GCC (extended sense)'s own tree with the current
> >> license of the demangler. The libstdc++ and libgcj libraries are
> >> supposed to implement interfaces which expose the functionality of the
> >> demangler. They have licenses which are more permissive than the GPL.
> >> We cannot link the demangler into these libraries, or its license
> >> would force us to apply the GPL's restrictions to them as well.
> >> Therefore we cannot implement all the interfaces that users expect.
> >
> > Is this why std::typeinfo::name() is still returning the mangled names
> > instead of human-readable ones?
>
> No; that is because the ABI standard specifies that it return mangled
> names.
>
> You're then supposed to be able to call the demangler -- but that's
> the bit that's missing.
Ah, thank you.
--
Ross Smith ...................................... Auckland, New Zealand
r-smith@ihug.co.nz ......................... http://storm.net.nz/~ross/
"We need a new cosmology. New gods. New sacraments. Another drink."
-- Patti Smith