Custom Query (1030 matches)

When running a loop-back test for an extended period of time, the computer goes into screen saving mode, and Clozure server sockets shut down, refusing any further (re)connections. This is not a one-time event. I see it repeatedly after many such trials.

The message from the client side, after receiving a time out on an awaited reply, and then attempting to reconnect, is:

Error making TCP connection: host="Amethyst.local", service=12010,

reason=Failed to connect: Connection refused (61).

(That (61) may be a locally generated error? or it may be a Unix error number?)

Given the new features for streams, namely the :sharing and :external-format improvements, it would be nice to be able to specify these keyword arguments for streams when doing something like:

(process-run-function "foo" #'foo :input :stream :output :stream)

I think having new keyword parameters like :input-args etc. would be better than adding a new keyword for each parameter (i.e. :input-sharing, :input-external-format, etc). Does this seem like a reasonable solution? (If so I can try to put a patch together to do this).

Alternatively, if a pipe stream creation API was exported (with support for these keyword options), then it would make it possible to create the pipe streams first, and simply pass them into process-run-function.

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.