Custom Query (1030 matches)

MAKE-SOCKET accepts timeout keyword arguments (:INPUT-TIMEOUT, :OUTPUT-TIMEOUT, and :CONNECT-TIMEOUT); non-null values of these arguments are supposed to be nonnegative REALs (according to the documentation) specifying time in seconds. (

Lower-level code (PROCESS-INPUT-WAIT, PROCESS-OUPUT-WAIT) takes optional timeout arguments which are required to be integers specifying time in milliseconds.

MAKE-SOCKET seems to just pass its timeout arguments unmodified to the lower-level code. Wackiness ensues (in the formm of type-errors). See ticket:1242.

I don't know whether this bug was newly introduced or if it's been present for a long time.

From #ccl on irc, user ecyrb:

(defmacro mk-arr (type init &optional len)
  "Make array with elements of TYPE, initializing."
  (if len `(make-array ,len :element-type ,type :initial-element ,init)
      `(make-array (length ,init) :element-type ,type
        :initial-contents ,init)))

(eval '(the (simple-array simple-string (2))
            (mk-arr 'simple-string '("Jan" "Feb"))))

;Compiler warnings : 
;   In an anonymous lambda form: Undefined function MK-ARR 
> Error: Special operator or global macro-function MK-ARR can't be FUNCALLed or APPLYed 
> While executing: #<Anonymous Function #x30004112FDDF>, in process listener(1). 

meta-. on, e.g. DEFUN, brings you to a point a few hundred characters after the start of the definition of defun (which happens to be a few hundred lines into its source file). The source file is using the CRLF convention, which is apparently confusing meta-.