Custom Query (1030 matches)

There's no NULL symbol defined by the standard.

ccl -n -e '(progn (format t "~a" (symbol-package (find-symbol "NULL"))) (quit))'

=> #<Package "COMMON-LISP">

There seems to be some odd behavior in RESTART-CASE when a restart clause has both test and interactive expressions.

In the attached file, the only difference between TEST-BROKEN-RESTART and TEST-WORKING-RESTART is that the latter’s restart clause has no test expression.

./dx86cl64 --no-init
Welcome to Clozure Common Lisp Version 1.9-dev-r15272M-trunk  (DarwinX8664)!
? (load "~/broken-restart.lisp")
#P"/Users/greg/broken-restart.lisp"

This case behaves correctly – the test fails, so the restart is not offered.

? (test-broken-restart 'non-restartable-error)
> Error: Condition #<NON-RESTARTABLE-ERROR #x30200072ED8D>
1 > :r
>   Type (:C <n>) to invoke one of the following restarts:
0. Return to break level 1.
1. #<RESTART ABORT-BREAK #x7EBECD>
2. Return to toplevel.
3. #<RESTART ABORT-BREAK #x7EC5AD>
4. Reset this thread
5. Kill this thread
1 > :pop

This case fails – the test passes and the restart is offered, but when the restart is selected, rather than calling the interactive expression, some anonymous restart is used, and another error is signaled.

? (test-broken-restart 'restartable-error)
> Error: Condition #<RESTARTABLE-ERROR #x302000726B1D>
1 > :r
>   Type (:C <n>) to invoke one of the following restarts:
2. #<RESTART BROKEN #x7EC16D>
1 > :c 2
Invoking restart: NIL
432345564230164480 is not of type (OR SYMBOL FUNCTION), and can't be FUNCALLed or APPLYed
1 > :pop

This is the same as the previous case, but with the test expression removed. This time it works – the restart is selected, then it interactively asks for a value.

? (test-working-restart 'restartable-error)
> Error: Condition #<RESTARTABLE-ERROR #x302000721A6D>
1 > :r
>   Type (:C <n>) to invoke one of the following restarts:
2. #<RESTART WORKING #x7EC16D>
1 > :c 2
Invoking restart: #<RESTART WORKING #x7EC16D>
Enter a value: 5
5
? 

There are inconsistencies in the documentation of the character sets ​http://ccl.clozure.com/ccl-documentation.html#Supported-Character-Encodings

:latin,3 instead of :latin-3 :cp68,7 instead of :cp68-8

on one hand, and on the other, inconsistencies in the naming of some character set, namely, why :latin-2 when the others are :latin1 :latin3 and :latin4 ?

cl-user> (dolist (cs '(:latin1 :latin2 :latin3 :latin4
                       :latin-1 :latin-2 :latin-3 :latin-4
                       :latin 3 
                       :cp63-7  :cp63 7))
           (handler-case 
               (progn
                 (close (open "/tmp/a.txt" :direction :probe :external-format cs))
                 (format t "~S~%" cs))
             (error (err)
               (format t "~S --> ~A~%" cs err))))
:latin1
:latin2 --> Invalid external-format: :latin2
:latin3
:latin4
:latin-1 --> Invalid external-format: :latin-1
:latin-2
:latin-3 --> Invalid external-format: :latin-3
:latin-4 --> Invalid external-format: :latin-4
:latin --> Invalid external-format: :latin
3 --> Invalid external-format: 3
:cp63-7 --> Invalid external-format: :cp63-7
:cp63 --> Invalid external-format: :cp63
7 --> Invalid external-format: 7
nil
cl-user> 

Another point, which is probably related, is that there's no introspection function to get the list of character sets and their aliases. Yes, there's a describe-character-encodings function but it gives a human readable string, that's in no way guaranteed to be parseable. I'd suggest a function returning a lisp a-list of name and aliases, so that programs can learn what encodings are supported by the current version of ccl. The documentation could then automatically be generated from this function, and no inconsistency would be to be expected.