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

> * Jean Louis <[email protected]> [2017-03-27 17:21:18 +0300]:
>
> 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:
>
>          (input (with-open-stream (str *standard-input*)

I told you that this use of with-open-stream makes no sense.
Joerg told you the same thing.
You just closed your *standard-input* and, of course, you are getting
the error:

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

Jean, this is _your_ error, not a CLISP bug.
You wrote invalid code and now you are being told that the code is
invalid for the 3rd time.

Recommended reading:
http://clisp.org/impnotes/streams-interactive.html#stream-stdio-init
http://clisp.org/impnotes/stream-eltype.html#bin-stdio


-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://mideasttruth.com
http://camera.org http://no2bds.org http://honestreporting.com http://jij.org
If money were measured in piles, I would have had a pit of it.

------------------------------------------------------------------------------
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