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: Bo Thorsen <bo at sonofthor dot dk>
- To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>,Mark Mitchell <mark at codesourcery dot com>
- Cc: Jason Merrill <jason at redhat dot com>, Robert Dewar <dewar at gnat dot com>,"apm35 at student dot open dot ac dot uk" <apm35 at student dot open dot ac dot uk>,"gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Fri, 22 Mar 2002 08:45:16 +0100
- Subject: Re: GCC to open the C++ demangle API?
- Organization: SuSE Labs
- References: <wvlofhjxtw6.fsf@prospero.cambridge.redhat.com> <6870000.1016660614@gandalf.codesourcery.com> <20020322173927.A9685@hg.cs.mu.oz.au>
On Friday 22 March 2002 07:40, Fergus Henderson wrote:
> On 20-Mar-2002, Mark Mitchell <mark@codesourcery.com> wrote:
> > > True, though I'm not aware of other approaches. But I definitely agree
> > > that this stuff has no place in the language standard.
> >
> > We're wandering into never-never land, but I do know of one other
> > approaches that have Really Been Used: interpretation, where the
> > lookup was done following the language rules, rather than by mangled
> > name.
> >
> > In practice, though, everyone uses mangling.
>
> For the .NET CLR, name mangling is not used; the underlying assembler,
> object file format, and linker directly support overloading.
... and it is by choice that existing systems do not do this. There's no
technical reason this couldn't be done as an ELF extension.
Bo.
--
Bo Thorsen | Praestevejen 4
Free software developer | 5290 Marslev
SuSE Labs | Denmark