I don't understand why this code behaves differently in different implementations:
(format t "asdf")
(setq var (read))
In CLISP it behaves as would be expected, with the prompt printed followed by the read, but in SBCL it reads, then outputs. I read a bit on the internet and changed it:
(format t "asdf")
(force-output t)
(setq var (read))
This, again, works fine in CLISP, but in SBCL it still reads, then outputs. I even tried separating it into another function:
(defun output (string)
(format t string)
(force-output t))
(output "asdf")
(setq var (read))
And it still reads, then outputs. Am I not using force-output
correctly or is this just an idiosyncrasy of SBCL?
All output functions in LISP take an optional argument called output-stream, where the output is sent. If not mentioned or nil, output-stream defaults to the value of the variable *standard-output*. Sr.No. Both write the object to the output stream specified by :stream, which defaults to the value of *standard-output*.
Format is a function in Common Lisp that can produce formatted text using a format string similar to the printf format string.
You need to use FINISH-OUTPUT
.
In systems with buffered output streams, some output remains in the output buffer until the output buffer is full (then it will be automatically written to the destination) or the output buffer is explicity emptied.
Common Lisp has three functions for that:
FINISH-OUTPUT
, attempts to ensure that all output is done and THEN returns.
FORCE-OUTPUT
, starts the remaining output, but IMMEDIATELY returns and does NOT wait for all output being done.
CLEAR-OUTPUT
, tries to delete any pending output.
Also the T
in FORCE-OUTPUT
and FORMAT
are unfortunately not the same.
force-output
/ finish-output
: T
is *terminal-io*
and NIL
is *standard-output*
FORMAT
: T
is *standard-output*
this should work:
(format t "asdf")
(finish-output nil) ; note the NIL
(setq var (read))
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With