Custom Query (1030 matches)

When I try to load usocket, an error "Foreign function not found: WIN64::|gethostname|" is displayed.

I am running CCL 64-bit on Windows 7 64-bit.

wx86cl64.exe -I ccl.save Welcome to Clozure Common Lisp Version 1.9-r15765 (WindowsX8664)! ? (ql:quickload "usocket") To load "usocket":

Load 1 ASDF system:

usocket

; Loading "usocket" Read error between positions 220 and 317 in C:/Users/Gerry/quicklisp/dists/quicklisp/software/usocket-0.6.0.1/backend/openmcl.lisp.

Error: Foreign function not found: WIN64::|gethostname| While executing: CCL::LOAD-EXTERNAL-FUNCTION, in process listener(1). Type :POP to abort, :R for a list of available restarts. Type :? for other options.

1 >

The error seems to be in the following code:

(defun get-host-name ()

(ccl::%stack-block ((resultbuf 256))

(when (zerop (#_gethostname resultbuf 256))

(ccl::%get-cstring resultbuf))))

Consider the following:

(format nil "~<{~;~{~,3f~^, ~:_~}~;};~:>"
        (list (loop for x from 0 to 30 collecting (expt 1.065 x))))

Under sbcl and LW this puts 11 or 10 (respectively) numbers per line. On CCL (1.7-dev-r14672M-trunk) it does not, returning everything on a single line.

This is a pretty esoteric format string, and it's possible I'm completely misunderstanding what it should do, but I *think* CCL is doing something wrong.

ClozureCL seems to switch to scientific notation when doing format ~F before the number becomes too large or small.

Example:

CCL> (format t "~F" 0.0001)
1.0E-4  ;; Expected: 0.0001

From CLHS Section 22.3.3.1:

If w is omitted, then if the magnitude of arg is so large (or, if d is also omitted, so small) that more than 100 digits would have to be printed, then an implementation is free, at its discretion, to print the number using exponential notation instead, as if by the directive ~E (with all parameters to ~E defaulted, not taking their values from the ~F directive).

I read that to mean that if less than 100 digits would be printed, then it's required to use fixed point representation.

MCL 5.0 actually gets this right, so I/we/somebody might be able to merge code from MCL's Lib/format.lisp into CCL's file of the same name.