Custom Query (1030 matches)

(copied from openmcl-devel, see also #1247 as it seems to be related)

Hi folks,

(in Clozure CL 1.10)

could there be a bug in `l1-sockets.lisp:859-860', where timeout values (supposedly in seconds) are not converted to the proper millisecond values used by PROCESS-INPUT-WAIT (`l1-streams.lisp:5449')? The documentation says (emphasis added):

input-timeout---The number of seconds before an input operation times out. Must be a real number between zero and one million. If an input operation takes longer than the specified number of seconds, an input-timeout error is signalled. (see Section 10.1.4, “Stream Timeouts and Deadlines”)

output-timeout---The number of seconds before an output operation times out. Must be a real number between zero and one million. If an output operation takes longer than the specified number of seconds, an output-timeout error is signalled. (see Section 10.1.4, “Stream Timeouts and Deadlines”)

I have not followed the rabbit hole to full length, but I am getting I/O timeout conditions on streams with i/o-timeout == 10 way before 10 seconds. It being actually interpreted as 10 milliseconds would make sense.

Try this to verify (this blocks for 10 seconds when I run it):

(with-open-socket (s :remote-host "mr.gy"

:remote-port 80 :input-timeout (* 10 1000))

(read-line s))

Regards, max

Trying to use nil as a function-name in defun crashes CCL 1.11. I think it should signal an error instead. I propose to change ccl::validate-function-name like so:

*** /usr/lib/ccl/level-0/l0-def.lisp
--- #<buffer l0-def.lisp>
***************
*** 118,124 ****
    name))
  
  (defun validate-function-name (name)
!   (if (symbolp name)
      name
      (if (setf-function-name-p name)
        (setf-function-name (cadr name))
--- 118,124 ----
    name))
  
  (defun validate-function-name (name)
!   (if (and (symbolp name) (not (null name)))
      name
      (if (setf-function-name-p name)
        (setf-function-name (cadr name))

I haven’t actually tested this (redefining validate-function-name on a running CCL leads to bootstrapping issues, don’t know how to avoid that).

I like to start my Common Lisp scripts with #!/usr/bin/env ccl. But when I load them in the CCL interpreter, I get an error:

Undefined character #\! in a #\# dispatch macro.

Could CCL include shebangs as ordinary CL syntax? CLISP and SBCL do.