Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] Diff of /sml/trunk/HISTORY
ViewVC logotype

Diff of /sml/trunk/HISTORY

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 660, Thu Jun 15 04:40:56 2000 UTC revision 671, Mon Jun 19 02:02:32 2000 UTC
# Line 12  Line 12 
12  Tag: <post-commit CVS tag>  Tag: <post-commit CVS tag>
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15    Name: Matthias Blume
16    Date: 2000/06/19 11:05:00 JST
17    Tag: blume-20000619-chdir-bugfix
18    Description:
19    
20    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
21    
22    ----------------------------------------------------------------------
23    Name: Matthias Blume
24    Date: 2000/06/18 22:00:10 JST
25    Tag: blume-20000618-implicit-anchors-really-gone
26    Description:
27    
28    I updates the previous HISTORY entry where I forgot to mention that
29    implicit anchors are no longer with us.
30    
31    The current update also gets rid of the (now useless) controller
32    CM.Control.implicit_anchors.
33    
34    ----------------------------------------------------------------------
35    Name: Matthias Blume
36    Date: 2000/06/16 17:30:00 JST
37    Tag: blume-20000616-anchorenv
38    Description:
39    
40    This patch implements the long anticipated (just kidding :) "anchor
41    environment" mechanism.  In the course of doing this, I also
42    re-implemented CM's internal "SrcPath" module from scratch.  The new
43    one should be more robust in certain boundary cases.  In any case, it
44    is a lot cleaner than its predecessor (IMHO).
45    
46    This time, although there is yet another boot file format change, I
47    kept the unpickler backward-compatible.  As a result, no new bootfiles
48    are necessary and bootstrapping is straightforward.  (You cannot read
49    new bootfiles into an old system, but the other way around is no
50    problem.)
51    
52    Visible changes:
53    
54    ** 0. Implicit path anchors (without the leading $-symbol) are no
55    longer recognized at all. This means that such path names are not
56    illegal either.  For example, the name basis.cm simply refers to a
57    local file called "basis.cm" (i.e, the name is an ordinary path
58    relative to .cm-files directory).  Or, to put it differently, only
59    names that start with $ are anchored paths.
60    
61    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
62    vanished.
63    
64    John (Reppy) had critizised this as soon as I originally proposed and
65    implemented it, but at that time I did not really deeply believe
66    him. :) Now I came full-circle because I need the $<singlearc> syntax
67    in another place where it cannot be seen as an abbreviation for
68    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
69    seems to mean (i.e., it "expands" into the corresponding anchor
70    value).
71    
72    However, when paths are used as members in CM description files, it
73    continues to be true that there must be at least another arc after the
74    anchor.  This is now enforced separately during semantic analysis
75    (i.e., from a lexical/syntactical point of view, the notation is ok.)
76    
77    ** 2. The "cm" class now accepts an option "bind".  The option's value
78    is a sub-option list of precisely two items -- one labeled "anchor"
79    and the other one labeled "value".  As you might expect, "anchor" is
80    used to specify an anchor name to be bound, and "value" specifies what
81    the anchor is being bound to.
82    
83    The value must be a directory name and can be given in either standard
84    syntax (including the possibility that it is itself an anchored path)
85    or native syntax.
86    
87    Examples:
88    
89       foo.cm (bind:(anchor:bar value:$mystuff/bar))
90       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
91    
92    and so on.
93    
94    The meaning of this is that the .cm-file will be processed with an
95    augmented anchor environment where the given anchor(s) is/are bound to
96    the given values(s).
97    
98    The rationale for having this feature is this: Suppose you are trying
99    to use two different (already stable) libraries a.cm and b.cm (that
100    you perhaps didn't write yourself).  Further, suppose each of these
101    two libraries internally uses its own auxiliary library $aux/lib.cm.
102    Normally you would now have a problem because the anchor "lib" can not
103    be bound to more than one value globally.  Therefore, the project that
104    uses both a.cm and b.cm must locally redirect the anchor to some other
105    place:
106    
107       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
108       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
109    
110    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
111    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
112    
113    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
114    you when you do so at the time of CM.stabilize).  Therefore, you can
115    also use an anchored path as the value:
116    
117      a.cm (bind:(anchor:lib value:$a-lib))
118      b.cm (bind:(anchor:lib value:$b-lib))
119    
120    Now you can globally configure (using the usual CM.Anchor.anchor or
121    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
122    itself is always locally bound, setting it globally is no longer
123    meaningful or necessary (but it does not hurt either).  In fact, "lib"
124    can still be used as a global anchor for separate purposes.  As a
125    matter of fact, one can locally define "lib" in terms of a global
126    "lib":
127    
128      a.cm (bind:(anchor:lib value:$lib/a))
129      b.cm (bind:(anchor:lib value:$lib/b))
130    
131    ** 3: The encoding of path names has changed.  This affects the way
132    path names are shown in CM's progress report and also the internal
133    protocol encoding used for parallel make.
134    
135    The encoding now uses one or more ':'-separated segments.  Each
136    segments corresponds to a file that has been specified relative to the
137    file given by its preceding segment.  The first segment is either
138    relative to the CWD, absolute, or anchored.  Each segment itself is
139    basically a Unix pathname; all segments but the first are relative.
140    
141    Example:
142    
143       $foo/bar/baz.cm:a/b/c.sml
144    
145    This path denotes the file bar/a/b/c.sml relative to the directory
146    denoted by anchor "foo".  Notice that the encoding also includes
147    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
148    paths are resolved relative to the .cm-files directory, so baz.cm must
149    be ignored to get the "real" pathname.
150    
151    To make this fact more obvious, CM puts the names of such "virtual
152    arcs" into parentheses when they appear in progress reports. (No
153    parentheses will appear in the internal protocol encoding.)  Thus,
154    what you really see is:
155    
156      $foo/bar/(baz.cm):a/b/c.sml
157    
158    I find this notation to be much more informative than before.
159    
160    Another new feature of the encoding is that special characters
161    including parentheses, colons, (back)slashes, and white space are
162    written as \ddd (where ddd is the decimal encoding of the character).
163    
164    *** The CM manual still needs to be updated.
165    
166    ----------------------------------------------------------------------
167  Name: Allen Leung  Name: Allen Leung
168  Date: 2000/06/15 00:38:00  Date: 2000/06/15 00:38:00
169  Tag: leunga-20000615-x86-peephole  Tag: leunga-20000615-x86-peephole

Legend:
Removed from v.660  
changed lines
  Added in v.671

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