--- doc/trunk/src/release-notes/110.79-README.html 2015/09/27 02:59:53 4138 +++ doc/trunk/src/release-notes/110.79-README.html 2015/09/27 13:42:48 4139 @@ -26,10 +26,23 @@ .code { font-family: "Courier", monospace; white-space: pre; + color: darkblue; } span.code { font-size: smaller; } + span.kw { + font-family: "Courier", monospace; + font-weight: bold; + color: darkgreen; + } + span.com { + font-style: italic; + color: indianred; + } + span.exe { + font-weight: bold; + } table.buglist { margin-left: 2em; } @@ -116,10 +129,22 @@

It is very unlikely that these changes will break existing code, but there are - a few scenarios in which the code might break. - (For example, the MLRISC library had two modules that implemented + a couple of scenarios in which the code might break. The first is conflicts created + by the use of open. For example, the implementation + of ml-yacc had declarations of the form +

+ open Array List +
+ which created a type error because List.sub shadowed + Array.sub. +

+

+ The second class of problem is when a module implements one of the affected Basis + signatures. For example, the MLRISC library had two modules that implemented extensions of the ARRAY signature and which required - modification to compile.) + modification to compile. +

+

In such cases, we recommend update the source code, but it is also possible to compile against the old version of the Basis Library by changing the line

@@ -159,9 +184,9 @@ properly nest into conventional block comments. For example, the following block comment is well formed:
- (* + (* fun f x = x (*) my identity function *) - *) + *)
  • Click to toggle
    does not end with </html> tag
    does not end with </body> tag
    The output has ended thus: com">(* fun f x = x (*) my identity function *) - *) + *)</span> </div> </li> <li>