- Jan 27, 2011
-
-
rtoy authored
attribute-table-limit and if the newvalue is #'read-token, we don't actually add the entry to the character-macro-hash-table, because that is the default value for the hash-table. This helps to keep the hash-table size small.
-
- Jan 21, 2011
-
-
rtoy authored
we produce 32-bit binaries instead of the default 64-bit (on 10.6 and later).
-
- Jan 07, 2011
-
-
rtoy authored
freebsd and solaris/x86.
-
- Dec 27, 2010
-
-
rtoy authored
FIND-FOREIGN-FUNCTION-NAME.
-
- Dec 26, 2010
- Dec 22, 2010
- Dec 19, 2010
-
-
rtoy authored
NIL. (From Paul Foley.)
-
- Dec 13, 2010
-
-
rtoy authored
LOAD-DOMAIN return an appropriate entry instead of returning NIL. This still gets rid of all the stats. Solution from Paul Foley.
-
- Dec 11, 2010
-
-
rtoy authored
caused by all the calls to stat in PROBE-FILE in LOCATE-DOMAIN-FILE for files that did not exist. The default locale was C, so every message lookup was causing many stat's to non-exist files. (There were over 1000 calls/sec on a 750 MHz sparc!) So we cache all the calls to PROBE-FILE in LOCATE-DOMAIN-FILE. But just in case, we also allow the user to get at the hash table to examine it (GET-DOMAIN-FILE-CACHE) and also allow the user to clear it (CLEAR-DOMAIN-FILE-CACHE) in case new translations are added without restarting lisp.
-
- Dec 09, 2010
-
-
rtoy authored
-
rtoy authored
the start. This was due to one of two things: The result sequence was created with a negative length, creating invalid objects, or accessing the invalid object would cause a segfault. code/seq.lisp: o Declare the type of LENGTH in MAKE-SEQUENCE-OF-TYPE better. It's not a fixnum, but an index (non-negative fixnum). This should catch any mistakes where we try to create sequences of negative length. o Explicitly catch invalid START and END indices in VECTOR-SUBSEQ* and LIST-SUBSEQ* and signal an error general-info/release-20c.txt: o Document bugfix.
-
- Dec 05, 2010
-
-
rtoy authored
o Fix typo in callback examples. o Add package qualifiers so the examples can be used in CL-USER.
-
- Nov 30, 2010
-
-
rtoy authored
Foley.) o While we're here, canonicalize *FILENAME-ENCODING* using the actual external format name.
-
- Nov 16, 2010
-
-
rtoy authored
Didier Verna, cmucl-imp, 2010-11-11.
-
- Nov 12, 2010
-
-
rtoy authored
a 64-bit boundary. Add st-pad3 to make sure st-blocks is on a 64-bit boundary. Only a problem when cross-compiling from a different arch. The native compile correctly padded the fields.
-
- Nov 10, 2010
-
-
rtoy authored
and entry size. Not yet used anywhere. This change needs a cross-compile; use boot-2010-11-1-cross.lisp as the cross-compile script. compiler/backend.lisp: o Add the two new slots to the backend. compiler/dump.lisp: o DUMP-DATA-MAYBE-BYTE-SWAPPING needs to handle (unicode) strings o DUMP-DATA-MAYBE-BYTE-SWAPPING should not swap bytes of a string. Genesis will make that happen. code/exports.lisp: o Export BACKEND-FOREIGN-LINKAGE-SPACE-START and BACKEND-FOREIGN-LINKAGE-ENTRY-SIZE. bootfiles/20b/boot-2010-11-1-cross.lisp: o Cross-compile script for this change.
-
- Nov 08, 2010
- Nov 04, 2010
-
-
rtoy authored
-
- Nov 02, 2010
-
-
rtoy authored
option. Bug noted by Didier Verna, cmucl-help, 2010-11-02.
-
- Oct 26, 2010
-
-
rtoy authored
-
- Oct 13, 2010
-
-
rtoy authored
compiled with and without Unicode. This is needed so that the pot files have the same content for both unicode and non-unicode builds. (The _"" and _N"" are handled by the reader, so things that are conditionalized out still get processed, unlike using gettext.)
-
- Oct 12, 2010
-
-
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.)
-
- 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 26, 2010
-
-
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*.
-
- Sep 24, 2010
-
-
rtoy authored
need to call octets-to-string-counted to setup the octet count array correctly. o Minor cleanup of code.
-
- Sep 21, 2010
-
-
rtoy authored
original completions along with the extensions.
-
- 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
: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
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
-
-
rtoy authored
Redo this by looping over all codepoints and selecting the codepoints that are Hangul syllables.
-
rtoy authored
o Update constants to Unicode version 5.2.0. i18n/unidata.bin: o Regenerated using Unicode version 5.2.0.
-
rtoy authored
o Just add some comments on why we don't put the dictionaries in unidata.bin. o Print out some messages when building the hangul and cjk dictionaries so the user knows what's happening. tools/build-unidata.lisp: o Add some comments on the various parts of unidata.bin.
-
- Sep 17, 2010
-
-
rtoy authored
o Export STRING-TO-NFC, UNICODE-COMPLETE, and UNICODE-COMPLETE-NAME. unidata.lisp: o Add explicit exports.
-