Changes between Version 10 and Version 11 of ReleaseNotes/1.9

Feb 15, 2013, 11:33:22 PM (6 years ago)



  • ReleaseNotes/1.9

    v10 v11  
    9595ticket:869 ticket:1012 ticket:989 ticket:933 ticket:881 ticket:1055 ticket:1050 ticket:1054 ticket:1049 ticket:1053 ticket:1052 ticket:1046 ticket:1045 ticket:1042 ticket:1041 ticket:1040 ticket:1038 ticket:1036 ticket:1037 ticket:682 ticket:1035 ticket:1033 ticket:933 ticket:1031 ticket:1030 ticket:1015 ticket:1027 ticket:1018 ticket:975 ticket:1011 ticket:1013 ticket:968 ticket:1005 ticket:1007 ticket:1000 ticket:996 ticket:992 ticket:985 ticket:980 ticket:981 ticket:926 ticket:977 ticket:976 ticket:858 and others
     97Many math function bugs fixed, thanks to David Findlay.
    9799== Notes ==
    98100The FASL version changed: FASL file produced with earlier versions of CCL won't work with this version and vice versa.
    150152If the first line of a text file contains an Emacs-style file-options line (";;; -*- .... -*-") and the file is opened for input with an :EXTERNAL-FORMAT of :INFERRED, then the value of the "coding" option (if present) is used to determine the file's CHARACTER-ENCODING.  (:EXTERNAL-FORMAT :INFERRED also tries to determine the file's line-termination as it has previously.)  When called with :EXTERNAL-FORMAT :DEFAULT, LOAD and COMPILE-FILE both arrange to call OPEN with an :EXTERNAL-FORMAT argument of :INFERRED.
     154=== (Hopefully) clearer error message when ARRAY-TOTAL-SIZE-LIMIT exceeded ===
     155ARRAY-TOTAL-SIZE-LIMIT is (ASH 1 24) in 32-bit versions of CCL and (ASH 1 56) in 64-bit versions.  This limit affects both the total number of elements in a CL array and the total size of other kinds of "vector-like" objects (BIGNUMs, FUNCTIONs on some platforms, etc.)  When the very low-level code that allocates vector-like objects finds that it's being asked to allocate something whose number of elements would meet or exceed this limit, it's historically signaled a TYPE-ERROR, complaining that one of its arguments is not of type (UNSIGNED-BYTE [24|56]).  While technically correct, users have found this error confusing (especially since they may not have explicitly requested the allocation.)
     156This situation now signals (via ERROR) a particular kind of STORAGE-CONDITION, and the report function for that condition tries to describe the kind of object being allocated and to explain why the allocation failed.
     158=== Argument string encoding in RUN-PROGRAM ===
     159On Unix systems, an OS-level process receives an argument count and a vector of #\NUL-terminated C strings as arguments; the C runtime system arranges to pass these arguments to the application's main() function (where they're conventionally named 'argc' and 'argv').  RUN-PROGRAM now arranges to encode the strings (in 'argv') in the encoding specified by its :EXTERNAL-FORMAT argument.
    154160== New exported symbols ==
    155161The following new symbols are now exported from the CCL package: