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 691, Tue Jul 25 07:20:24 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/07/25 16:20:00 JST
17    Tag: blume-20000725-makedepend
18    Description:
19    
20    Added a script called ml-makedepend.  This can be used in makefiles
21    for Unix' make in a way very similar to the "makedepend" command for
22    C.
23    
24    The script internally uses function CM.sources.
25    
26    Synopsis:
27    
28        ml-makedepend [-f makefile] cmfile targetname
29    
30    The default for the makefile is "makefile" (or "Makefile" should
31    "makefile" not exist).
32    
33    ml-makedepend adds a cmfile/targetname-specific section to this
34    makefile (after removing the previous version of this section).  The
35    section contains a single dependency specification with targetname on
36    the LHS (targetname is an arbitrary name), and a list of files derived
37    from the cmfile on the RHS.  Some of the files on the RHS are
38    ARCH/OPSYS-specific.  Therefore, ml-makedepend inserts references to
39    "make" variables $(ARCH) and $(OPSYS) in place of the corresponding
40    path names.  The makefile writer is responsible for making sure that
41    these variables have correct at the time "make" is invoked.
42    
43    ----------------------------------------------------------------------
44    Name: Matthias Blume
45    Date: 2000/07/22 23:30:00 JST
46    Tag: blume-20000722-urlupdate
47    Description:
48    
49    Changed BOOT and config/srcarchiveurl to point to BL server:
50    
51        ftp://ftp.research.bell-labs.com/dist/smlnj/working/110.29/
52    
53    ----------------------------------------------------------------------
54    Name: Matthias Blume
55    Date: 2000/07/18 18:00:00 JST
56    Tag: blume-20000718-Version_110_29
57    Description:
58    
59    1. Updated src/compiler/TopLevel/main/version.sml to version 110.29
60    
61    2. Updated config/version to 110.29
62    
63    3. Updated config/srcarchiveurl
64    
65    3. New boot files!
66       ftp://ftp.cs.princeton.edu/pub/people/blume/sml/110.29-autofetch
67    
68    ----------------------------------------------------------------------
69    Name: Matthias Blume
70    Date: 2000/07/11 13:58:00 JST
71    Tag: blume-20000711-doctypo
72    Description:
73    
74    Fixed a few typos in CM manual.
75    
76    ----------------------------------------------------------------------
77    Name: Allen Leung
78    Date: 2000/06/15 00:38:00
79    Tag: leunga-20000704-sparc-x86
80    
81    1. x86 peephole improvement sp += k; sp -= k => nop  [from John]
82    2. fix to x86 RET bug [found by Dan Grossman]
83    3. sparc assembly bug fix for ticc instructions [found by Fermin]
84    
85       Affects c-- and moby only
86    
87    ----------------------------------------------------------------------
88    Name: Matthias Blume
89    Date: 2000/07/04 15:26:00
90    Tag: blume-20000704-trigger
91    Description:
92    
93    1. Improvements to CM manual.
94    2. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
95       of getting a back-trace.  The function, when called, raises an
96       internal exception which explicitly carries the full back-trace history,
97       so it is unaffected by any intervening handle-raise pairs ("trivial"
98       or not).  The interactive loop will print that history once it arrives
99       at top level.
100       Short of having all exceptions implicitly carry the full history, the
101       recommended way of using this facility is:
102         - compile your program with instrumentation "on"
103         - run it, when it raises an exception, look at the history
104         - if the history is "cut off" because of some handler, go and modify
105           your program so that it explicitly calls BTrace.trigger
106         - recompile (still instrumented), and rerun; look at the full history
107    
108    ----------------------------------------------------------------------
109    Name: Matthias Blume
110    Date: 2000/07/03 15:36:00 JST
111    Tag: blume-20000702-manual
112    Description:
113    
114    Small corrections and updates to CM manual.
115    
116    ----------------------------------------------------------------------
117    Name: Matthias Blume
118    Date: 2000/06/29 16:04:00 JST
119    Tag: blume-20000629-yacctool
120    Description:
121    
122    Changes:
123    
124    1. Class "mlyacc" now takes separate arguments to pass options to
125       generated .sml- and .sig-files independently.
126    2. Corresponding CM manual updates.
127    3. BTrace module now also reports call sites.  (However, for loop clusters
128       it only shows from where the cluster was entered.)  There are associated
129       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
130    
131    ----------------------------------------------------------------------
132    Name: Matthias Blume
133    Date: 2000/06/27 16:51:00 JST
134    Tag: blume-20000627-noweb
135    Description:
136    
137    Changes:
138    
139     1. Implemented "subdir" and "witness" options for noweb tool.
140        This caused some slight internal changes in CM's tool implementation.
141     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
142        some remaining issues from earlier path anchor changes.
143     3. Updated CM manual accordingly.
144    
145     4. Changed implementation of back-tracing so that I now consider it
146        ready for prime-time.
147    
148        In particular, you don't have to explicitly trigger the back-trace
149        anymore.  Instead, if you are running BTrace-instrumented code and
150        there is an uncaught exception (regardless of whether or not it was
151        raised in instrumented code), the top-level evalloop will print
152        the back-trace.
153    
154        Features:
155    
156          - Instrumented and uninstrumented code work together seemlessly.
157            (Of course, uninstrumented code is never mentioned in actual
158             back-traces.)
159    
160          - Asymptotic time- and space-complexity of instrumented code is
161            equal to that of uninstrumented code.  (This means that
162            tail-recursion is preserved by the instrumentation phase.)
163    
164          - Modules whose code has been instrumented in different sessions
165            work together without problem.
166    
167          - There is no penalty whatsoever on uninstrumented code.
168    
169          - There is no penalty on "raise" expressions, even in
170            instrumented code.
171    
172        A potential bug (or perhaps it is a feature, too):
173    
174          A back-trace reaches no further than the outermost instrumented
175          non-trivial "raise".  Here, a "trivial" raise is one that is the
176          sole RHS of a "handle" rule.  Thus, back-traces reach trough
177    
178               <exp> handle e => raise e
179    
180          and even
181    
182               <exp> handle Foo => raise Bar
183    
184          and, of course, through
185    
186               <exp> handle Foo => ...
187    
188         if the exception was not Foo.
189    
190         Back-traces always reach right through any un-instrumented code
191         including any of its "handle" expressions, trivial or not.
192    
193       To try this out, do the following:
194    
195         - Erase all existing binfiles for your program.
196           (You may keep binfiles for those modules where you think you
197            definitely don't need back-tracing.)
198         - Turn on back-trace instrumentation:
199              SMLofNJ.Internals.BTrace.mode (SOME true);
200         - Recompile your program.  (I.e., run "CM.make" or "use".)
201         - You may now turn instrumentation off again (if you want):
202              SMLofNJ.Internals.BTrace.mode (SOME false);
203         - Run your program as usual.  If it raises an exception that
204           reaches the interactive toplevel, then a back-trace will
205           automatically be printed.  After that, the toplevel loop
206           will print the exception history as usual.
207    
208    ----------------------------------------------------------------------
209    Name: Matthias Blume
210    Date: 2000/06/26 09:56:46 JST
211    Tag: blume-20000626-setup
212    Description:
213    
214    CM: - setup-parameter to "sml" added; this can be used to run arbitrary
215          ML code before and after compiling a file (e.g., to set compiler
216          flags)
217    
218    Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
219              - associated changes to btrace.sml (BTrace instrumentation pass)
220              - cleaner implementation of btimp.sml (BTrace tracing and report
221                module)
222    
223    CM manual: * new path encoding documented
224               * description of setup-parameter to "sml" added
225    
226    The biggest user-visible change to back-tracing is that it is no
227    longer necessary to compile all traced modules within the same
228    session.  (This was a real limitation.)
229    
230    ----------------------------------------------------------------------
231    Name: Matthias Blume
232    Date: 2000/06/24 12:40:00 JST
233    Tag: blume-20000624-startup
234    Description:
235    
236    Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
237    bit too often -- to put it mildly. :)
238    
239    ----------------------------------------------------------------------
240    Name: Matthias Blume
241    Date: 2000/06/23 18:20:00 JST
242    Tag: blume-20000623-btrace
243    Description:
244    
245    This updates adds a backtrace facility to aid programmers in debugging
246    their programs.  This involves the following changes:
247    
248    1. Module system/smlnj/init/core.sml (structure _Core) now has hooks for
249       keeping track of the current call stack.  When programs are compiled
250       in a special mode, the compiler will insert calls to these hooks
251       into the user program.
252       "Hook" means that it is possible for different implementations of
253       back-tracing to register themselves (at different times).
254    
255    2. compiler/MiscUtil/profile/btrace.sml implements the annotation phase
256       as an Absyn.dec->Absyn.dec rewrite.  Normally this phase is turned off.
257       It can be turned on using this call:
258         SMLofNJ.Internals.BTrace.mode (SOME true);
259       Turning it off again:
260         SMLofNJ.Internals.BTrace.mode (SOME false);
261       Querying the current status:
262         SMLofNJ.Internals.BTrace.mode NONE;
263       Annotated programs are about twice as big as normal ones, and they
264       run a factor of 2 to 4 slower with a dummy back-trace plugin (one
265       where all hooks do nothing).  The slowdown with a plugin that is
266       actually useful (such as the one supplied by default) is even greater,
267       but in the case of the default plugin it is still only an constant
268       factor (amortized).
269    
270    3. system/Basis/Implementation/NJ/internals.{sig,sml} have been augmented
271       with a sub-structure BTrace for controlling back-tracing.  In particular,
272       the above-mentioned function "mode" controls whether the annotation
273       phase is invoked by the compiler.  Another important function is
274       "trigger": when called it aborts the current execution and causes
275       the top-level loop to print a full back-trace.
276    
277    4. compiler/MiscUtil/profile/btimp.sml is the current default plugin
278       for back-tracing.  It keeps track of the dynamic call stack and in
279       addition to that it keeps a partial history at each "level" of that
280       stack.  For example, if a tail-calls b, b tail-calls c, and c tail-calls
281       d and b (at separate times, dynamically), then the report will show:
282    
283       GOTO   d
284             /c
285       GOTO  \b
286       CALL   a
287    
288       This shows that there was an initial non-tail call of a, then a
289       tail-call to b or c, looping behavior in a cluster of functions that
290       consist of b and c, and then a goto from that cluster (i.e., either from
291       b or from c) to d.
292    
293       Note that (depending on the user program) the amount of information
294       that the back-trace module has to keep track of at each level is bounded
295       by a constant.  Thus, the whole implementation has the same asymptotical
296       complexity as the original program (both in space and in time).
297    
298    5. compiler/TopLevel/interact/evalloop.sml has been modified to
299       handle the special exception SMLofNJ.Internals.BTrace.BTrace
300       which is raised by the "trigger" function mentioned above.
301    
302    Notes on usage:
303    
304    - Annotated code works well together with unannotated code:
305    Unannotated calls simply do not show up at all in the backtrace.
306    
307    - It is not a good idea to let modules that were annotated during
308    different sessions run at the same time.  This is because the compiler
309    chooses small integers to identify individual functions, and there
310    will be clashes if different modules were compiled in separate sessions.
311    (Nothing will crash, and you will even be told about the clashes, but
312    back-trace information will in general not be useful.)
313    
314    - Back-tracing can be confused by callcc and capture.
315    
316    - The only way of getting a back-trace right now is to explicitly
317    invoke the "trigger" function from your user program.  Eventually, we
318    should make every exception carry back-trace information (if
319    available).  But since this creates more overhead at "raise"-time
320    (similar to the current exnHistory overhead), I have not yet
321    implemented this.  (The implementation will be rather easy.)  With
322    exceptions carrying back-trace information, this facility will be even
323    more useful because users don't need to modify their programs...
324    
325    - While it is possible to compile the compiler with back-trace
326    annotations turned on (I did it to get some confidence in
327    correctness), you must make absolutely sure that core.sml and
328    btimp.sml are compiled WITHOUT annotation!  (core.sml cannot actually
329    be compiled with annotation because there is no core access yet, but
330    if you compile btimp.sml with annotation, then the system will go into
331    an infinite recursion and crash.)
332    Since CM currently does not know about BTrace, the only way to turn
333    annotations on and off for different modules of the compiler is to
334    interrupt CMB.make, change the settings, and re-invoke it.  Of course,
335    this is awkward and clumsy.
336    
337    Sample sessions:
338    
339    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
340    - SMLofNJ.Internals.BTrace.mode (SOME true);
341    [autoloading]
342    [autoloading done]
343    val it = false : bool
344    - structure X = struct
345    -     fun main n = let
346    -         fun a (x, 0) = d x
347    -           | a (x, n) = b (x, n - 1)
348    -         and b (x, n) = c (x, n)
349    -         and c (x, n) = a (x, n)
350    -         and d x = e (x, 3)
351    -         and e (x, 0) = f x
352    -           | e (x, n) = e (x, n - 1)
353    -         and f 0 = SMLofNJ.Internals.BTrace.trigger ()
354    -           | f n = n * g (n - 1)
355    -         and g n = a (n, 3)
356    -     in
357    -         f n
358    -     end
359    - end;
360    structure X : sig val main : int -> int end
361    - X.main 3;
362    *** BACK-TRACE ***
363    GOTO   stdIn:4.2-13.20: X.main[2].f
364    GOTO-( stdIn:4.2-13.20: X.main[2].e
365    GOTO   stdIn:4.2-13.20: X.main[2].d
366         / stdIn:4.2-13.20: X.main[2].a
367         | stdIn:4.2-13.20: X.main[2].b
368    GOTO-\ stdIn:4.2-13.20: X.main[2].c
369    CALL   stdIn:4.2-13.20: X.main[2].g
370    GOTO   stdIn:4.2-13.20: X.main[2].f
371    GOTO-( stdIn:4.2-13.20: X.main[2].e
372    GOTO   stdIn:4.2-13.20: X.main[2].d
373         / stdIn:4.2-13.20: X.main[2].a
374         | stdIn:4.2-13.20: X.main[2].b
375    GOTO-\ stdIn:4.2-13.20: X.main[2].c
376    CALL   stdIn:4.2-13.20: X.main[2].g
377    GOTO   stdIn:4.2-13.20: X.main[2].f
378    GOTO-( stdIn:4.2-13.20: X.main[2].e
379    GOTO   stdIn:4.2-13.20: X.main[2].d
380         / stdIn:4.2-13.20: X.main[2].a
381         | stdIn:4.2-13.20: X.main[2].b
382    GOTO-\ stdIn:4.2-13.20: X.main[2].c
383    CALL   stdIn:4.2-13.20: X.main[2].g
384    GOTO   stdIn:4.2-13.20: X.main[2].f
385    CALL   stdIn:2.15-17.4: X.main[2]
386    -
387    
388    (Note that because of a FLINt bug the above code currently does not
389    compile without BTrace turned on.)
390    
391    Here is another example, using my modified Tiger compiler:
392    
393    Standard ML of New Jersey v110.28.1 [FLINT v1.5], June 5, 2000
394    - SMLofNJ.Internals.BTrace.mode (SOME true);
395    [autoloading]
396    [autoloading done]
397    val it = false : bool
398    - CM.make "sources.cm";
399    [autoloading]
400    ...
401    [autoloading done]
402    [scanning sources.cm]
403    [parsing (sources.cm):parse.sml]
404    [creating directory CM/SKEL ...]
405    [parsing (sources.cm):tiger.lex.sml]
406    ...
407    [wrote CM/sparc-unix/semant.sml]
408    [compiling (sources.cm):main.sml]
409    [wrote CM/sparc-unix/main.sml]
410    [New bindings added.]
411    val it = true : bool
412    - Main.compile ("../testcases/merge.tig", "foo.out");
413    *** BACK-TRACE ***
414    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trvar
415    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
416    CALL   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
417    GOTO   lib/semant.sml:289.3-295.22: SemantFun[2].transExp.trexp.check[2]
418    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
419    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
420    CALL   lib/semant.sml:488.3-505.6: SemantFun[2].transDec.trdec[2].transBody[2]
421         / lib/semant.sml:411.65-543.8: SemantFun[2].transDec
422    CALL-\ lib/semant.sml:413.2-540.9: SemantFun[2].transDec.trdec[2]
423    CALL   lib/semant.sml:99.2-396.21: SemantFun[2].transExp.trexp
424    CALL   lib/semant.sml:8.52-558.4: SemantFun[2].transProg[2]
425    CALL   main.sml:1.18-118.4: Main.compile[2]
426    -
427    
428    ----------------------------------------------------------------------
429    Name: Matthias Blumen
430    Date: 2000/06/21 18:00:00 JST
431    Tag: blume-20000621-manual
432    Description:
433    
434    CM manual update: Path environments documented.
435    
436    ----------------------------------------------------------------------
437    Name: Matthias Blume
438    Date: 2000/06/19 13:40:00
439    Tag: blume-20000619-manual
440    Description:
441    
442    CM manual and system/README update.  This only covers the fact that
443    there are no more implicit anchors.  (Path environments and the "bind"
444    option to "cm" have yet to be documented.)
445    
446    ----------------------------------------------------------------------
447    Name: Matthias Blume
448    Date: 2000/06/19 11:05:00 JST
449    Tag: blume-20000619-chdir-bugfix
450    Description:
451    
452    Fixed a bug in new SrcPath module that sometimes led to a bad chDir call.
453    
454    ----------------------------------------------------------------------
455    Name: Matthias Blume
456    Date: 2000/06/18 22:00:10 JST
457    Tag: blume-20000618-implicit-anchors-really-gone
458    Description:
459    
460    I updates the previous HISTORY entry where I forgot to mention that
461    implicit anchors are no longer with us.
462    
463    The current update also gets rid of the (now useless) controller
464    CM.Control.implicit_anchors.
465    
466    ----------------------------------------------------------------------
467    Name: Matthias Blume
468    Date: 2000/06/16 17:30:00 JST
469    Tag: blume-20000616-anchorenv
470    Description:
471    
472    This patch implements the long anticipated (just kidding :) "anchor
473    environment" mechanism.  In the course of doing this, I also
474    re-implemented CM's internal "SrcPath" module from scratch.  The new
475    one should be more robust in certain boundary cases.  In any case, it
476    is a lot cleaner than its predecessor (IMHO).
477    
478    This time, although there is yet another boot file format change, I
479    kept the unpickler backward-compatible.  As a result, no new bootfiles
480    are necessary and bootstrapping is straightforward.  (You cannot read
481    new bootfiles into an old system, but the other way around is no
482    problem.)
483    
484    Visible changes:
485    
486    ** 0. Implicit path anchors (without the leading $-symbol) are no
487    longer recognized at all. This means that such path names are not
488    illegal either.  For example, the name basis.cm simply refers to a
489    local file called "basis.cm" (i.e, the name is an ordinary path
490    relative to .cm-files directory).  Or, to put it differently, only
491    names that start with $ are anchored paths.
492    
493    ** 1. The $<singlearc> abbreviation for $/<singlearc> has finally
494    vanished.
495    
496    John (Reppy) had critizised this as soon as I originally proposed and
497    implemented it, but at that time I did not really deeply believe
498    him. :) Now I came full-circle because I need the $<singlearc> syntax
499    in another place where it cannot be seen as an abbreviation for
500    $/<singlearc>.  To avoid the confusion, $<singlearc> now means what it
501    seems to mean (i.e., it "expands" into the corresponding anchor
502    value).
503    
504    However, when paths are used as members in CM description files, it
505    continues to be true that there must be at least another arc after the
506    anchor.  This is now enforced separately during semantic analysis
507    (i.e., from a lexical/syntactical point of view, the notation is ok.)
508    
509    ** 2. The "cm" class now accepts an option "bind".  The option's value
510    is a sub-option list of precisely two items -- one labeled "anchor"
511    and the other one labeled "value".  As you might expect, "anchor" is
512    used to specify an anchor name to be bound, and "value" specifies what
513    the anchor is being bound to.
514    
515    The value must be a directory name and can be given in either standard
516    syntax (including the possibility that it is itself an anchored path)
517    or native syntax.
518    
519    Examples:
520    
521       foo.cm (bind:(anchor:bar value:$mystuff/bar))
522       lib.cm (bind:(anchor:a value:"H:\\x\\y\\z"))  (* only works under windows *)
523    
524    and so on.
525    
526    The meaning of this is that the .cm-file will be processed with an
527    augmented anchor environment where the given anchor(s) is/are bound to
528    the given values(s).
529    
530    The rationale for having this feature is this: Suppose you are trying
531    to use two different (already stable) libraries a.cm and b.cm (that
532    you perhaps didn't write yourself).  Further, suppose each of these
533    two libraries internally uses its own auxiliary library $aux/lib.cm.
534    Normally you would now have a problem because the anchor "lib" can not
535    be bound to more than one value globally.  Therefore, the project that
536    uses both a.cm and b.cm must locally redirect the anchor to some other
537    place:
538    
539       a.cm (bind:(anchor:lib value:/usr/lib/smlnj/a-stuff))
540       b.cm (bind:(anchor:lib value:/usr/lib/smlnj/b-stuff))
541    
542    This hard-wires $lib/aux.cm to /usr/lib/smlnj/a-stuff/aux.cm or
543    /usr/lib/smlnj/b-stuff/aux.cm, respectively.
544    
545    Hard-wiring path names is a bit inflexible (and CM will verbosely warn
546    you when you do so at the time of CM.stabilize).  Therefore, you can
547    also use an anchored path as the value:
548    
549      a.cm (bind:(anchor:lib value:$a-lib))
550      b.cm (bind:(anchor:lib value:$b-lib))
551    
552    Now you can globally configure (using the usual CM.Anchor.anchor or
553    pathconfig machinery) bindings for "a-lib" and "b-lib".  Since "lib"
554    itself is always locally bound, setting it globally is no longer
555    meaningful or necessary (but it does not hurt either).  In fact, "lib"
556    can still be used as a global anchor for separate purposes.  As a
557    matter of fact, one can locally define "lib" in terms of a global
558    "lib":
559    
560      a.cm (bind:(anchor:lib value:$lib/a))
561      b.cm (bind:(anchor:lib value:$lib/b))
562    
563    ** 3: The encoding of path names has changed.  This affects the way
564    path names are shown in CM's progress report and also the internal
565    protocol encoding used for parallel make.
566    
567    The encoding now uses one or more ':'-separated segments.  Each
568    segments corresponds to a file that has been specified relative to the
569    file given by its preceding segment.  The first segment is either
570    relative to the CWD, absolute, or anchored.  Each segment itself is
571    basically a Unix pathname; all segments but the first are relative.
572    
573    Example:
574    
575       $foo/bar/baz.cm:a/b/c.sml
576    
577    This path denotes the file bar/a/b/c.sml relative to the directory
578    denoted by anchor "foo".  Notice that the encoding also includes
579    baz.cm which is the .cm-file that listed a/b/c.sml.  As usual, such
580    paths are resolved relative to the .cm-files directory, so baz.cm must
581    be ignored to get the "real" pathname.
582    
583    To make this fact more obvious, CM puts the names of such "virtual
584    arcs" into parentheses when they appear in progress reports. (No
585    parentheses will appear in the internal protocol encoding.)  Thus,
586    what you really see is:
587    
588      $foo/bar/(baz.cm):a/b/c.sml
589    
590    I find this notation to be much more informative than before.
591    
592    Another new feature of the encoding is that special characters
593    including parentheses, colons, (back)slashes, and white space are
594    written as \ddd (where ddd is the decimal encoding of the character).
595    
596    *** The CM manual still needs to be updated.
597    
598    ----------------------------------------------------------------------
599  Name: Allen Leung  Name: Allen Leung
600  Date: 2000/06/15 00:38:00  Date: 2000/06/15 00:38:00
601  Tag: leunga-20000615-x86-peephole  Tag: leunga-20000615-x86-peephole

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

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