The encoding is done (only) in basicTypes/OccName.lhs. The
comments are below... but they could always be inaccurate.
Trust only the code. (On this occasion, I think the comment
is correct, though.)
Before things appear in .hc or .o files, and in -ddump traces,
they are 'z-encoded'. So '$' appears as 'zd' etc. Details in
basicTypes/OccName.lhs.
We havn't checked out the profiler, remember.
Simon
Here's our convention for splitting up the interface file name space:
d... dictionary identifiers
(local variables, so no name-clash worries)
$f... dict-fun identifiers (from inst decls)
$m... default methods
$p... superclass selectors
$w... workers
$T... compiler-generated tycons for dictionaries
$D... ...ditto data cons
$sf.. specialised version of f
in encoded form these appear as Zdfxxx etc
:... keywords (export:, letrec: etc.)
> -----Original Message-----
> From: Alex Ferguson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, February 10, 1999 5:26 PM
> To: [EMAIL PROTECTED]
> Subject: Uncompiling internal names...
>
>
>
> What do "$m" identifiers correspond to? I'm getting one of these lob
> up in a -prof -auto cost centre, and I don't know what/where/how it
> corresponds to.
>
>
> While I'm on the general topic, any hints'n'tips on decoding $d's?
>
> In a name like $dEqPriority0, I presume the first two elements
> are Class and Type, but does the "0" relate to the method, or is
> it just a name-supply artifact?
>
> Slan,
> Alex.
>
