SCM Repository

[smlnj] Diff of /sml/trunk/src/compiler/MAP

[smlnj] / sml / trunk / src / compiler / MAP

Diff of /sml/trunk/src/compiler/MAP

-revision 1465, Thu Mar  4 22:30:03 2004 UTC
+revision 1466, Thu Mar  4 23:33:35 2004 UTC
 Line 37
     * modules and signatures, signature matching, functor application
     * code found in directories Semant, ElabData, Elaborator
+ [***
+  What is the distinction between Basics and Semant?  Should these be
+  merged?  How about ElabData?  Some of these files (Semant/types) might
+  also fit there.
+  We have Basics/*, Semant/basics, ElabData/basics, and Elaborator/basics.
+  What is the rationale telling us what goes in each of these places?
+  This complex organization seems to be partially motivated by the goal
+  of separating out any features that are SML/NJ-specific from the generic
+  SML stuff.
+ ***]
  Basics
    mlcomp/
+     basic front-end data structures (e.g. symbols, stamps, ...)
      symbol.sig/sml      -- symbols (should be in ElabData?)
      fastsymbol.sig/sml  -- fast symbols (should be in ElabData?)
      fixity.sml          -- fixity properties (should be in ElabData)
-Line 46
+Line 61
      persmap.sml         -- finite maps over pids (persistent stamps)
      pidenv.sig/sml      -- environments using pid (persistant stamps) as keys
      compileexn.sml      -- Compile exception (where used?)
-   miscutil/  (why not in MiscUtil?)
+   miscutil/
+     some left-over stuff (why not in MiscUtil?  may be redundant)
      intstrmap.sig/sml   -- int/string maps for use in environments;
                             appears redundant with IntStrMapV defined in
                             Env (ElabData/basics/env.sml)
                             used in Tuples, ElabCore, Parse/lex/tokentable.sml.
    errormsg/
-     errormsg.sig/sml    -- error messages
+     error messages
+       errormsg.sig/sml    -- error message interface
    source/
+     -- the source abstraction + file pathnames
      pathnames.sig/sml   -- file path names
      source.sig/sml      -- input source datastructure
      sourcemap.sig/sml   -- map character positions in source to line no/column
                             supporting #line "declaration"
    print/
+     -- some printing support (more elsewhere?)
      pp-wrapper.sml      -- implements old PP interface using new SML/NJ Lib PP
      printutil.sig/sml   -- some print utilities (uses Symbol)
-     printcontrol.sml    -- print control flags, out, say
+       printcontrol.sml    -- print control flags; out, say functions
    stats/
      stats.sml           -- facilities for defining timed phases
    main/
      basiccontrol.sml    -- printWarning control flag, topregistry
                             uses ControlRegistry, Controls
-Line 72
+Line 96
  Semant
    basics/
+     -- some "basic" stuff -- why not in Basics?
      inlinfo.sig/sml     -- inlining info (?)
    elaborate/
-     elabmod.sml         -- module level elaboration (why not in Elaborator)
+     -- module level, top level elaboration (why not under Elaborator?)
+       elabmod.sml         -- module level elaboration
      elabtop.sml         -- top-level elaboration
    modules/
-     evalent.sml
+     -- mechanisms for module elaboration.  "Entity" is the static-phase
-     instantiate.sml
+        computation element associated with a module (a kind of expression).
-     instantiate-param.sml
+        entity expressions are basically a typed lambda calculus
-     module-plists.sml
+       evalent.sml         -- evaluation of entity expressions
-     sigmatch.sml
+       instantiate.sml     -- create a free "realization" from a signature
+       instantiate-param.sml  -- like instantiate.sml, but different (how?)
+       module-plists.sml   -- ???
+       sigmatch.sml        -- signature matching (the type-checking of modules)
-   pickle/   -- pickling static environments
+   pickle/
+     -- pickling static environments (the non-"new" variants should go away?)
      pickle-sym-pid.sml
      unpickle-sym-pid.sml
      pickmod-new.sml
-Line 93
+Line 123
      rehash.sml
    statenv/
+     -- hand made primitive types, constructors, etc.
      prim.sml
    types/
+     -- some types stuff [why not in ElabData/types?]
      cproto.sml
      tp-var-info.sml
      types-reformat.sml
-Line 103
+Line 135
  ElabData
+   -- data structures and utilities used in elaboration
    basics/
+     -- some basic data structures used in elaboration
      lambdavar.sig/sml
        lambda variables, the abstract representation of variables, used
        as roots of dynamic access chains
-Line 120
+Line 154
        SymPath and InvPath: direct and inverse symbolic paths (selecting
        module components)
      ii.sml [FLINT]
-       FLINT related information for inlining (why is this in elaborator?)
+         FLINT related information for inlining (why is this in the elaborator?)
      lambdavar.sig/sml
        lambda variables, the abstract representation of variables
      core-ptnum.sml
-Line 129
+Line 163
        defines the special structure symbol "_Core" used to access certain
        special bindings (e.g Match and Bind exceptions)
-   syntax/   -- (typed) abstract syntax
+   syntax/
+     -- (typed) abstract syntax
      absyn.sig/sml   -- the abstract syntax types
      varcon.sig/sml  -- variable and data constructor representations
      absynutil.sml   -- utility functions for building tuple patterns and expressions
-   types/    -- representing, constructing and manipulating types
+   types/
+     -- representing, constructing and manipulating types
      types.sig/sml      -- the representation of SML types
      typesutil.sig/sml  -- large collection of utility functions for working with types
      tuples.sml         -- fns for constructing tuple and record types
      core-basictypes.sml -- building the primitive types and associated values
    statenv/
+     -- representation and mechanism for static environments
      bindings.sig/sml   -- the basic binding forms (values, types, signatures, etc.)
      statenv.sig/sml    -- instantiate generic environments with ML bindings
      lookup.sig/sml     -- accessing symbols in environments
-Line 148
+Line 185
      coreacc.sml        -- access components of the _Core structure
      browse.sml         -- "browsing" the static environment (???)
-   modules/   -- representation of modules
+   modules/
+     -- representation of modules
      modules.sig/sml    -- representation of modules and signatures
      moduleutil.sig/sml -- lots of utility functions for modules
      moduleid.sml       -- module identities used in Modmaps ???
-Line 157
+Line 195
      epcontext.sml      --
    main/
+     -- control flags and contex parameters
      compinfo.sml       -- elaboration context parameter
      edcontrol.sig/sml  -- control flags for ElabData
  Elaborator
+   -- the actual elaboration
    basics/
      elabcontrol.sml    -- Elaborator control flags

 Legend:



Removed from v.1465
 


changed lines


 
Added in v.1466
 Legend:



Removed from v.1465
 


changed lines


 
Added in v.1466
-Removed from v.1465
+Added in v.1466

root@smlnj-gforge.cs.uchicago.edu	ViewVC Help
Powered by ViewVC 1.0.0