- Oct 12, 2010
-
-
rtoy authored
-
rtoy authored
of streams. This is a change from current 20a and 20b behavior which didn't signal errors, but matches the behavior for releases 19f and earlier. But allow them to work on binary-text-streams. This is the same behavior as before for binary-text-stream streams. However, read-sequence no longer allows reading from streams into arbitrary objects, unless the stream is a binary-text-stream stream. code/fd-stream-extfmt.lisp: o In %SET-FD-STREAM-EXTERNAL-FORMAT, only update fd-stream-in/fd-stream-out if we have a character or binary-text-stream stream. o Don't update the fd-stream-string-buffer or lisp-stream-in-buffer if we have a binary-text-stream because that will mess up how fast-read-char and fast-read-byte dispatch to do the right thing for binary-text-stream streams. code/fd-stream.lisp: o Set the fd-stream-in and fd-stream-bin slots appropriately depending on whether we have a character, binary, or binary-text-stream stream. o Only create the lisp-stream-in-buffer if we do NOT have a binary-text-stream. (Binary streams didn't use the lisp-stream-buffer previously, so no change there. Character streams use the lisp-stream-buffer and/or lisp-string-buffer.) o Set the fd-stream-flags appropriately for the kind of stream this is. Checking a fixnum is faster than checking the type of a stream. code/struct.lisp: o Add FLAGS slot to LISP-STREAM so we can tell what kind of stream (character, binary, binary-text-stream) we have. code/sysmacs.lisp: o Change FAST-READ-CHAR so that if we have a have a binary or binary-text-stream stream, we dispatch to the fast-read-char methods to do the right thing, including signaling an error for the wrong kind of stream. o Change FAST-READ-BYTE so that if we do not have a binary stream, we dispatch to the fast-read-char method to do the right thing. compiler/dump.lisp: o With the above changes, we can no longer write characters to a binary stream, like a FASL file. Make the fasl file a binary-text-stream so that we can. (Alternatively, we could create the FASL header as a string, convert to octets and dump the octest to the file. This is easier, and should still be fast for writing fasls.)
-
- Oct 10, 2010
-
-
rtoy authored
strings instead of having several slightly different versions all over.
-
rtoy authored
-
rtoy authored
-
rtoy authored
object to its value.
-
rtoy authored
name correctly for unicode strings. It stopped after the first 0 byte, which basically means either nothing or a single byte is printed. Just dump out the entire UTF-16 octets in native byte order.
-
- Oct 06, 2010
-
-
rtoy authored
-
- Sep 30, 2010
-
-
rtoy authored
o Describe how arch and os are derived if they're not specified on the command line.
-
- Sep 29, 2010
-
-
rtoy authored
as the key for the composition table. That way the logic is in exactly one place and not spread out through the code.
-
- Sep 27, 2010
- Sep 26, 2010
-
-
rtoy authored
-
rtoy authored
we weren't because *cmucl-lib* is almost always bound. Normally *old-cmucl-library-search-list* is unbound, but when a core is made, it becomes bound. We use that to indicate that the library search list should be set to *old-cmucl-library-search-list*.
-
rtoy authored
always part of the build now, we can remove most of the conditionalization on FEATURE_EXECUTABLE. Only need to preserve the part about calling map_core_sections, which is only defined if FEATURE_EXECUTABLE is defined.
-
- Sep 25, 2010
- Sep 24, 2010
-
-
rtoy authored
-
rtoy authored
should be handled. compiler/main.lisp: o Add DECODING-ERROR slot to SOURCE-INFO structure. o MAKE-FILE-SOURCE-INFO requires a decoding error argument so the SOURCE-INFO structure can be properly initialized. o Add :DECODING-ERROR keyword arg to COMPILE-FILE to specify how decoding errors are handled. Default is T, which means to signal an error. compiler/fndb.lisp: o Tell compiler about the new parameter. general-info/release-20c.txt: o Document change.
-
rtoy authored
dirname being undefined.
-
rtoy authored
need to call octets-to-string-counted to setup the octet count array correctly. o Minor cleanup of code.
-
- Sep 21, 2010
- Sep 20, 2010
-
-
rtoy authored
notes now. o Tell the compiler what type the first return value of CODEPOINT is. Apparently, the compiler can't figure that out itself.
-
rtoy authored
pot files.
-
rtoy authored
-
rtoy authored
-
rtoy authored
-
rtoy authored
:EXTERNAL-FORMAT keyword argument to specify the format to use for any streams that RUN-PROGRAM needs to create. Patch from Paul Foley.
-
rtoy authored
case we were returning the prefix string, but that would be incorrect if the prefix string is not a valid character. So check that it is valid and return it. Otherwise do nothing (thereby returning nil) so slime can note the character is invalid.
-
rtoy authored
more and fix some bugs in previous change.
-
- Sep 19, 2010
-
-
rtoy authored
(because they're so simple). o Add some comments for %STR. o Change implementation of %MATCH to be simpler and add comments on why we do what we do and explain what happens if we don't. o Handle completion of Hangul syllables better: - Match "Hangul_S" instead of "Hangul_Syllable" because there's #\Hangul_Single_Dot_Tone_Mark. - If we match "Hangul_S", try to complete some Hangul syllables so we don't fool slime into thinking "Hangul_Syllable_" is the only completion. There are obviously more. o Handle completion of CJK Unified Ideographs better by trying to complete more so slime isn't fooled into thinking "CJK_Unified_Ideograph-" is the only possible completion.
-
rtoy authored
-
rtoy authored
-
rtoy authored
given the wrong split value.
-
rtoy authored
the constraints on the codebook, we just sort them in descreasing order of length. o In %MIP, it might happen that MISMATCH returns NIL, which means a match. In this case, don't change the position.
-
- Sep 18, 2010