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 675, Fri Jun 23 09:18:18 2000 UTC revision 680, Mon Jul 3 06:35:55 2000 UTC
# Line 13  Line 13 
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15  Name: Matthias Blume  Name: Matthias Blume
16    Date: 2000/07/02 15:36:00 JST
17    Tag: blume-20000702-manual
18    Description:
19    
20    Small corrections and updates to CM manual.
21    
22    ----------------------------------------------------------------------
23    Name: Matthias Blumen
24    Date: 2000/06/29 16:04:00 JST
25    Tag: blume-20000629-yacctool
26    Description:
27    
28    Changes:
29    
30    1. Class "mlyacc" now takes separate arguments to pass options to
31       generated .sml- and .sig-files independently.
32    2. Corresponding CM manual updates.
33    3. BTrace module now also reports call sites.  (However, for loop clusters
34       it only shows from where the cluster was entered.)  There are associated
35       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
36    
37    ----------------------------------------------------------------------
38    Name: Matthias Blume
39    Date: 2000/06/27 16:51:00 JST
40    Tag: blume-20000627-noweb
41    Description:
42    
43    Changes:
44    
45     1. Implemented "subdir" and "witness" options for noweb tool.
46        This caused some slight internal changes in CM's tool implementation.
47     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
48        some remaining issues from earlier path anchor changes.
49     3. Updated CM manual accordingly.
50    
51     4. Changed implementation of back-tracing so that I now consider it
52        ready for prime-time.
53    
54        In particular, you don't have to explicitly trigger the back-trace
55        anymore.  Instead, if you are running BTrace-instrumented code and
56        there is an uncaught exception (regardless of whether or not it was
57        raised in instrumented code), the top-level evalloop will print
58        the back-trace.
59    
60        Features:
61    
62          - Instrumented and uninstrumented code work together seemlessly.
63            (Of course, uninstrumented code is never mentioned in actual
64             back-traces.)
65    
66          - Asymptotic time- and space-complexity of instrumented code is
67            equal to that of uninstrumented code.  (This means that
68            tail-recursion is preserved by the instrumentation phase.)
69    
70          - Modules whose code has been instrumented in different sessions
71            work together without problem.
72    
73          - There is no penalty whatsoever on uninstrumented code.
74    
75          - There is no penalty on "raise" expressions, even in
76            instrumented code.
77    
78        A potential bug (or perhaps it is a feature, too):
79    
80          A back-trace reaches no further than the outermost instrumented
81          non-trivial "raise".  Here, a "trivial" raise is one that is the
82          sole RHS of a "handle" rule.  Thus, back-traces reach trough
83    
84               <exp> handle e => raise e
85    
86          and even
87    
88               <exp> handle Foo => raise Bar
89    
90          and, of course, through
91    
92               <exp> handle Foo => ...
93    
94         if the exception was not Foo.
95    
96         Back-traces always reach right through any un-instrumented code
97         including any of its "handle" expressions, trivial or not.
98    
99       To try this out, do the following:
100    
101         - Erase all existing binfiles for your program.
102           (You may keep binfiles for those modules where you think you
103            definitely don't need back-tracing.)
104         - Turn on back-trace instrumentation:
105              SMLofNJ.Internals.BTrace.mode (SOME true);
106         - Recompile your program.  (I.e., run "CM.make" or "use".)
107         - You may now turn instrumentation off again (if you want):
108              SMLofNJ.Internals.BTrace.mode (SOME false);
109         - Run your program as usual.  If it raises an exception that
110           reaches the interactive toplevel, then a back-trace will
111           automatically be printed.  After that, the toplevel loop
112           will print the exception history as usual.
113    
114    ----------------------------------------------------------------------
115    Name: Matthias Blume
116    Date: 2000/06/26 09:56:46 JST
117    Tag: blume-20000626-setup
118    Description:
119    
120    CM: - setup-parameter to "sml" added; this can be used to run arbitrary
121          ML code before and after compiling a file (e.g., to set compiler
122          flags)
123    
124    Compiler: - improved btrace API (in core.sml, internals.{sig,sml})
125              - associated changes to btrace.sml (BTrace instrumentation pass)
126              - cleaner implementation of btimp.sml (BTrace tracing and report
127                module)
128    
129    CM manual: * new path encoding documented
130               * description of setup-parameter to "sml" added
131    
132    The biggest user-visible change to back-tracing is that it is no
133    longer necessary to compile all traced modules within the same
134    session.  (This was a real limitation.)
135    
136    ----------------------------------------------------------------------
137    Name: Matthias Blume
138    Date: 2000/06/24 12:40:00 JST
139    Tag: blume-20000624-startup
140    Description:
141    
142    Fixes startup slowdown problem.  (I was calling SrcPath.sync a _tad_
143    bit too often -- to put it mildly. :)
144    
145    ----------------------------------------------------------------------
146    Name: Matthias Blume
147  Date: 2000/06/23 18:20:00 JST  Date: 2000/06/23 18:20:00 JST
148  Tag: blume-20000623-btrace  Tag: blume-20000623-btrace
149  Description:  Description:

Legend:
Removed from v.675  
changed lines
  Added in v.680

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