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 /doc/trunk/src/release-notes/110.79-README.html
ViewVC logotype

Diff of /doc/trunk/src/release-notes/110.79-README.html

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

revision 4138, Sun Sep 27 02:59:53 2015 UTC revision 4139, Sun Sep 27 13:42:48 2015 UTC
# Line 26  Line 26 
26    .code {    .code {
27      font-family: "Courier", monospace;      font-family: "Courier", monospace;
28      white-space: pre;      white-space: pre;
29        color: darkblue;
30    }    }
31    span.code {    span.code {
32      font-size: smaller;      font-size: smaller;
33    }    }
34      span.kw {
35        font-family: "Courier", monospace;
36        font-weight: bold;
37        color: darkgreen;
38      }
39      span.com {
40        font-style: italic;
41        color: indianred;
42      }
43      span.exe {
44        font-weight: bold;
45      }
46    table.buglist {    table.buglist {
47      margin-left: 2em;      margin-left: 2em;
48    }    }
# Line 116  Line 129 
129      </dl>      </dl>
130      <p style="margin-bottom: 0pt;">      <p style="margin-bottom: 0pt;">
131        It is very unlikely that these changes will break existing code, but there are        It is very unlikely that these changes will break existing code, but there are
132        a few scenarios in which the code might break.        a couple of scenarios in which the code might break.  The first is conflicts created
133        (For example, the <b>MLRISC</b> library had two modules that implemented        by the use of <span class="kw">open</span>.  For example, the implementation
134          of <span class="exe">ml-yacc</span> had declarations of the form
135          <div class="code">
136          <span class="kw">open</span> Array List
137          </div>
138          which created a type error because <span class="code">List.sub</span> shadowed
139          <span class="code">Array.sub</span>.
140        </p>
141        <p>
142          The second class of problem is when a module implements one of the affected Basis
143          signatures.  For example, the <b>MLRISC</b> library had two modules that implemented
144        extensions of the <span class="code">ARRAY</span> signature and which required        extensions of the <span class="code">ARRAY</span> signature and which required
145        modification to compile.)        modification to compile.
146        </p>
147        <p>
148        In such cases, we recommend update the source code, but it is also possible to compile        In such cases, we recommend update the source code, but it is also possible to compile
149        against the old version of the Basis Library by changing the line        against the old version of the Basis Library by changing the line
150      </p>      </p>
# Line 159  Line 184 
184          properly nest into conventional block comments.  For example, the following          properly nest into conventional block comments.  For example, the following
185          block comment is well formed:          block comment is well formed:
186          <div class=code>          <div class=code>
187          (*          <span class="com">(*
188          fun f x = x (*) my identity function *)          fun f x = x (*) my identity function *)
189          *)          *)</span>
190          </div>          </div>
191        </li>        </li>
192        <li>        <li>

Legend:
Removed from v.4138  
changed lines
  Added in v.4139

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