[m-rev.] for review: add a demangled name field to MR_ProcIds

[Zoltan Somogyi]

On 02-Jan-2002, Fergus Henderson <fjh at cs.mu.OZ.AU> wrote:
> > - That this module be in the library (probably with documentation suppressed
> >   as we currently do for e.g. private_builtin), so that we can replace all
> >   mangling/demangling code with calls to the code of this library module.
> >   This should not just the compiler, the old profiler and the deep profiler,
> >   but even include util/mdemangle.c, if we can solve the bootstrapping issue
> >   involved.
> 
> Why not in the "browser" directory, like browser/name_mangle.m?

At the moment, the browser library is linked into executables iff they are
compiled with debugging. The mangle/demangle module would need to be linked
into several programs (compiler, the profilers, mdemangle) regardless of
whether they are compiled with debugging. It therefore doesn't belong
in the browser library; it should be a separate library. It would therefore
make sense to put it into a directory other than the browser directory.

The obvious alternative to putting it into the standard library directory
is to create a new directory and .a/.so file specifically for it.

Zoltan.
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------