Re: Export bits of the demangler's internal interface

[Daniel Jacobowitz <drow at mvista dot com>]

On Sat, Jan 03, 2004 at 11:12:34AM -0500, DJ Delorie wrote:
> 
> > OK.  How about cp_v3_d_?  DJ, does this answer your concern about
> > namespace pollution?
> 
> Call me old fashioned, but I'd prefer demangler_*
> 
> The cp_v3_d_ has nothing in it that makes it unique to the demangler.
> It could easily be a function in gcc/cp that handles libg++-v3 double
> types.

Hmm - that doesn't say what it's a demangler for, but I guess it
doesn't much matter.  In fact, the other C++ demanglers could be made
to use the same output routines - it would make them consistent, and
probably faster - but I don't think it's really worth investing time in
them at this late date.

demangler_* or cp_demangler_* works for me.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer