This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: Demangling broken (was: Re: [PATCH] Demangler woes with current CVS and type names)
- From: Phil Edwards <phil at jaj dot com>
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>
- Cc: gcc-patches at gcc dot gnu dot org, binutils at sources dot redhat dot com
- Date: Thu, 31 Jan 2002 16:36:00 -0500
- Subject: Re: Demangling broken (was: Re: [PATCH] Demangler woes with current CVS and type names)
- References: <20020131123141.A10866@disaster.basement.lan> <200201311828.TAA12642@ignucius.axis.se>
On Thu, Jan 31, 2002 at 07:28:55PM +0100, Hans-Peter Nilsson wrote:
> > Does it ever make sense for any demangling anywhere -- i.e., for non-types --
> > to only partially consume a mangled string? (I wouldn't think so, but...)
>
> I don't know either, but supposedly it can stop at characters
> not in the mangled set. I don't remember if it has to eat all
> characters fed to it to be considered successful.
Hmm. Okay, I won't go that route.
> Either way seems a partial solution, solving the "data" ->
> "double" error, but not to the "d" -> "double" error.
Ah, I see the problem more clearly now; thanks. Yes, it looks like an option
is needed. I'll look into some kind of "no type demangling" flag somewhere.
Phil
--
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams