Changes between Version 2 and Version 3 of Commentary/Hpc

Timestamp:

12/07/06 20:59:18 (6 years ago)

Author:

andykam

Comment:

--

Commentary/Hpc

@@ -5 +5 @@
 The basic idea is this
  * For each (sub)expression in the Haskell Syntax, write the (sub)expression in a HsTick
- * Each HsTick has a module local index number.
+ * Each `HsTick` has a module local index number.
  * There is a table (The Mix datastructure) that maps this index number to original source location.
- * Each HsTick is mapped in the Desugar pass with: 
+ * Each `HsTick` is mapped in the Desugar pass with: 
 {{{
   dsExpr (HsTick n e) = case tick<modname,n> of DEFAULT -> e
 }}}
- * This tick is a special type of Id, a TickOpId which takes no core-level argument, but has two pre-applied arguments; the module name and the module-local tick number.
+ * This tick is a special type of `Id`, a `TickOpId` which takes no core-level argument, but has two pre-applied arguments; the module name and the module-local tick number.
    * We store both module name and tick number to allow this Id to be passed (inlined) inside other modules.
-   * This Id has type '''State# World#'''
+   * This `Id` has type '''State# World#'''
  * The core simplifier must not remove this case, but it can move it.
-   * The do-not-remove is inforced via the ... function in ....
-   * The semantics are tick if-and-when-and-as you enter the DEFAULT case. But a chain of consecative ticks can be executed in any order.
- * The CoreToStg Pass translates the ticks into StgTick
+   * The do-not-remove is enforced via the ... function in ....
+   * The semantics are tick if-and-when-and-as you enter the `DEFAULT` case. But a chain of consecutive ticks can be executed in any order.
+ * The CoreToStg Pass translates the ticks into `StgTick`
 {{{
   .. (case tick<m,n> of DEFAULT -> e) = .. StgTick m n (... e)
 }}}
- * The Cmm code generate translates StgTick to a 64 bit increment.
+ * The `Cmm` code generate translates `StgTick` to a 64 bit increment.
 
 TO BE CONTINUED.