Custom Query (1030 matches)
Results (898 - 900 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #907 | moved | Commandline parameter for shell scripting support | ||
| Description |
Wonder if it is possible or appropriate to add a commandline parameter just like SBCL's "--script" or ECL's "-shell" switch. Maybe it will accept the pathname of a file to skip the #! line ,load, execute and quit. Any arguments following that are not processed and collected into CCL:*UNPROCESSED-COMMAND-LINE-ARGUMENTS*, just like what "--" did. This can be useful, and I don't see it will break any compatibility. |
|||
| #1278 | fixed | (code-char #xFFFE) returns NIL at least on x86 and x86-64 | ||
| Description |
And (code-char #xFFFF) returns NIL too. Unicode Corrigendum 9 http://www.unicode.org/versions/corrigendum9.html explains that "noncharacters" should not be rejected. They are the codepoints U+FFFE U+FFFF U+1FFFE U+1FFFF ... up to U+10FFFE and U+10FFFF, plus the codepoints U+FDD0..U+FDEF. It states "the definition of noncharacter in the standard has led some implementers to interpret any presence of a noncharacter code point in a Unicode string as causing that string to be ill-formed, and thereby has led to inappropriate over-rejection" And later: noncharacters "are not illegal in interchange nor do they cause ill-formed Unicode text". Being able to represent codepoint U+FFFE is also important, because when found in a file or stream it is a strong diagnostic indication that the Unicode text was parsed incorrectly - typically the wrong UTF-16 endianity has been used. Replacing it with NIL is both non-standard (see Corrigendum 9 above) and makes troubleshooting more difficult. For these reasons, I am asking to change CODE-CHAR such that (code-char #xFFFE) returns #\U+FFFE and (code-char #\U+FFFF) returns #\U+FFFF |
|||
| #964 | duplicate | Tests fails for the MD5 library on 32 bit versions (windows and linux) | ||
| Description |
I run the tests included in the library. Only appears in 32 bit versions of 1.8, not in 1.7 and it works on Linux x64. I use MD5 library that is used by Hunchentoot (it fails inside it as well). |
|||
