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

Legend:
Removed from v.659  
changed lines
  Added in v.673

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