Re: How to solve: module 'syscalls' requires package OS

On Mon, Mar 27, 2017 at 10:08:40AM -0400, Sam Steingold wrote:
> >> I think I already said that this is a known bug
> >> https://sourceforge.net/p/clisp/bugs/695/
> >> with a known work-around (see the bug).
> >
> > I am not sure if that is the same bug.
> 
> Great!
> Please create a small isolated reproducible test case.

This one here:

(defun main nil
  (let* ((output '())
         (input (with-open-stream (str *standard-input*)
                  (loop :for line = (read-line *standard-input* nil nil)
                     :while line
                     :do (push line output)))))
    output))
;;(main)


That one works well as lisp.

And if I save memory image, and write two lines and press CTRL-D I get
following

*** - WRITE-CHAR on #<CLOSED IO SYNONYM-STREAM *TERMINAL-IO*> is illegal

*** - WRITE-CHAR on #<CLOSED IO SYNONYM-STREAM *TERMINAL-IO*> is illegal

*** - WRITE-CHAR on #<CLOSED IO SYNONYM-STREAM *TERMINAL-IO*> is illegal

*** - WRITE-CHAR on #<CLOSED IO SYNONYM-STREAM *TERMINAL-IO*> is illegal

*** - WRITE-CHAR on #<CLOSED IO SYNONYM-STREAM *TERMINAL-IO*> is illegal

forever



Jean

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-list