Custom Query (1030 matches)

%SET-CSTRING (which is the SETF inverse of %GET-CSTRING) tries to use %COPY-IVECTOR-TO-PTR; that can't work (since strings are always UTF-32 internally).

(This was originally part of ticket:241)

Reported in email:

I know this is an internal function, but I don't see any exported equivalent
functionality.  In any case, it appears the :start keyword argument is doing
something wrong.

Welcome to Clozure Common Lisp Version 1.2-r7902S  (LinuxX8664)!
? (ccl::decode-string-from-octets  (make-array 5 :element-type
'(unsigned-byte 8) :initial-element 65))
"AAAAA"
5
? (ccl::decode-string-from-octets  (make-array 5 :element-type
'(unsigned-byte 8) :initial-element 65) :start 1)
"AA"
3
? (ccl::decode-string-from-octets  (make-array 5 :element-type
'(unsigned-byte 8) :initial-element 65) :start 0)
"AAAAA"
5
? (ccl::decode-string-from-octets  (make-array 5 :element-type
'(unsigned-byte 8) :initial-element 65) :start 2)
""
1
? (ccl::decode-string-from-octets  (make-array 5 :element-type
'(unsigned-byte 8) :initial-element 65) :start 1)
"AA"
3


In this case it's skipping some extra octets.  But that's not the worst of
it.  "In the wild" I observed this function adding garbage to the end of the
string that is returned, if start > 0.

There have been reports that the editor hangs when trying to open CR-terminated text files in the editor.

One theory - that it may be an endianness issue - doesn't seem to be correct; I've been able to open CR-terminated files under both PPC and X8664, and haven't yet been able to reproduce this.