{"id":111841,"date":"2023-11-29T21:10:14","date_gmt":"2023-11-29T19:10:14","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-sbcl-2-3-11-realizaczii-yazyka-common-lisp"},"modified":"2023-11-29T21:10:14","modified_gmt":"2023-11-29T19:10:14","slug":"vypusk-sbcl-2-3-11-realizaczii-yazyka-common-lisp","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-sbcl-2-3-11-realizaczii-yazyka-common-lisp","title":{"rendered":"Release of SBCL 2.3.11, an implementation of the Common Lisp language","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of SBCL 2.3.11 (Steel Bank Common Lisp), a free implementation of the Common Lisp programming language, has been published. The project code is written in Common Lisp and C, and is distributed under the BSD license. In this new release: <\/p>\n
\n
Minor incompatibilities:\n
\n
Streams with the external-format parameter defined using «:REPLACEMENT» will apply the replacement data once in the stream, which leads to decoding errors (unlike in some cases, where it applies once for each byte sequence that is not a valid starting position for a character in this external-format).\n
External-format specifiers using unsupported or unrecognized options will now signal an error. <\/ul>\n
Improvements:\n
\n
In the dispatching of generic functions using the standard or short combination method, if there are no main applicable methods, the system will invoke the generic function SB-PCL:NO-PRIMARY-METHOD, whose standard behavior is to signal an error. Users can define methods for this generic function.\n
External formats now support newline variants for single-byte and UTF-8 encodings.\n
Errors regarding the encoding and decoding of characters signaled by stream or octet functions now support USE-VALUE restarting for handlers that provide replacements for input or output.\n
READ-SEQUENCE and WRITE-SEQUENCE support user-defined sequences; the standard implementation processes one element at a time, reading or writing one byte or character to\/from the stream respectively. <\/ul>\n
Optimizations:\n
\n
External formats with :REPLACEMENT no longer bind handlers for conversion function errors, which should reduce the number of cons operations and improve performance.\n
If :EXTERNAL-FORMAT acts as an argument for STRING-TO-OCTETS or OCTETS-TO-STRING and is a constant at compile-time, then the external format is resolved at load time, not at each invocation.\n
The compiler may restrict argument types for certain functions based on the inferred or implied type of the value returned by that function.\n
The compiler reduces the number of redundant type checks in functions like ASSOC and GETF. <\/ul>\n
Bug fixes:\n
\n
OCTETS-TO-STRING now correctly signals or applies replacements when using single-byte external formats for less common encodings (e.g., iso-8859-3), rather than taking bits from the NIL address and converting those bits to characters.\n
FILE-STRING-LENGTH now returns NIL if the input values are not encoded in an external stream format.\n
Table-based multi-byte external formats (EUC-JP, Shift-JIS, GBK) now consider the replacement character (in the external format or through restarting) when encoding to octets.\n
Converting from octets using external formats UCS-2, UCS-4, and UTF-32 no longer reads the end of the octet array with a non-integer number of two or four-byte units.\n
Converting from octets using external formats UCS-2, UCS-4, and UTF-32 now returns a simple string, as required by the OCTETS-TO-STRING type definition.\n
Using an incorrect external format argument for OPEN or WITH-OPEN-FILE (or the internal MAKE-FD-STREAM) no longer leads to a file descriptor leak.\n
SB-ROTATE-BYTE defines BYTE specifications beyond the allowable range before executing cons for very large integers for the use of masks and shifts.\n
Fixing the output type when compiling SB-ROTATE-BYTE forms with a non-zero POSITION in the byte definition.\n
Correcting multiple assembly errors when compiling MAKE-ARRAY, MAKE-STRING, and others with large constant sizes.\n
Fixing an internal error when compiling (SETF-SBIT) with a large constant index.\n
Fixing an internal compiler error for a lambda function with an incorrect parameter list in LABELS.\n
Fixing an internal compiler error when compiling certain infinitely-recursive LABELS forms.\n
Fixing an internal compiler error when attempting to embed a jump to an already removed label.\n
FILL-POINTER must never be negative. <\/ul>\n<\/ul>\n