Custom Query (1030 matches)
Results (697 - 699 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #787 | fixed | ccl:arglist interns into the current package | ||
| Description |
When used on macros, ccl:arglist interns symbols from the lambda list into the current package: (defpackage :foo (:use :cl)) #<Package "FOO"> ? (in-package :foo) #<Package "FOO"> ? (defmacro bar (bar10)) ;Compiler warnings : ; In BAR: Unused lexical variable BAR10 BAR ? (in-package :cl-user) #<Package "COMMON-LISP-USER"> ? (find-symbol "BAR10") NIL NIL ? (ccl:arglist 'foo::bar t) (BAR10) :DECLARATION ? (find-symbol "BAR10") BAR10 :INTERNAL |
|||
| #807 | fixed | ccl:macroexpand-all fails on flet of set functions | ||
| Description |
|
|||
| #680 | fixed | ccl:send-to says it can take a string arg, but it really can't. | ||
| Description |
Welcome to Clozure Common Lisp Version 1.6-dev-r13678M (DarwinX8664)! ? (defparameter *s* (make-socket :type :datagram)) *S* ? (send-to *s* "hey" 3 :remote-host "127.0.0.1" :remote-port 12345) > Error: value "hey" is not of the expected type (OR (ARRAY CHARACTER) > (ARRAY (UNSIGNED-BYTE 8)) > (ARRAY (SIGNED-BYTE 8))). > While executing: VERIFY-SOCKET-BUFFER, in process listener(1). > Type :POP to abort, :R for a list of available restarts. > Type :? for other options. 1 > verify-socket-buffer is actually checking for an 8-bit subtag, and with this new-fangled unicode thing, that doesn't include strings. My first inclination is to say that i/o on datagram sockets is done in octects. This requires the user to use encode-string-to-octects/decode-string-from-octets explicitly. It might also be work to pay attention to the socket object's external format and encode the string on the user's behalf, but if Gilgamesh wants to send a cuneiform string "foo", then the actual buffer length in octets isn't going to be 3. |
|||
