clisp+cygwin: ext:make-pipe-input/output/io-stream



Hello,

I am trying to drive gnuplot from clisp on windows+cygwin (yes I know,
I should just fork over the $500 for Alegro. But, a kid is going to
college). But, I get an error that I cannot figure out where it comes
from.

I define the output stream as

(defvar *gplot* (ext:make-pipe-io-stream "/bin/gnuplot"))

(I have tried both the unix and windows style paths with same
results. I am not trying the bi-directional declaration, because,
frankly, I don't know what to do with the resulting stream - I am
supposed to get three values, but get only one).

After opening up the stream, the following command sequence

(format *gplot* "plot sin(x)")
(finish-output *gplot*)

results in this error:
UNIX error 32 (EPIPE): Broken pipe, child process terminated or socket
closed
[Condition of type SYSTEM::SIMPLE-OS-ERROR]

I have also tried pointing to a nonexistent executable, with the same
result. So it seems that clisp will try to communicate only when I do
the (finish-output *gplot*) command.

I can understand the nomenclature (somewhat), but my understanding of
the internals of unix, windows & cygwin is lacking. I am not sure if
what I am trying to do is even possible with clisp on cygwin (I have
the latest clisp & cygwin).


Thanks,

Mirko
.



Relevant Pages

  • Re: clisp+cygwin: ext:make-pipe-input/output/io-stream
    ... I don't know what to do with the resulting stream - I am ... So it seems that clisp will try to communicate only when I do ... the (finish-output *gplot*) command. ... windows & cygwin is lacking. ...
    (comp.lang.lisp)
  • Re: clisp+cygwin: ext:make-pipe-input/output/io-stream
    ... I am trying to drive gnuplot from clisp on windows+cygwin (yes I know, ... I define the output stream as ... windows & cygwin is lacking. ... It should probably work identically on cygwin (modulo the path to gnuplot). ...
    (comp.lang.lisp)
  • Re: Lisp in a Box
    ... Mac OS X much less so. ... Unix implementation here] binary port from a set of instructions for Linux. ... Emacs and/or CLISP to start with rather than building them from scratch, ...
    (comp.lang.lisp)
  • Re: Why Lisp is not popular with average programmers
    ... >>> Perhaps what would be needed is MORE isolation. ... >> That sounds valid for CLISP, but not every Lisp tries to isolate you. ... >> You can for the most part happily ignore Unix and live in the Lisp ...
    (comp.lang.lisp)
  • Re: CLISP (Cygwin) defaults to :DOS instead of :UNIX
    ... this one is actually about CLISP! ... even though my Cygwin installation is set to use unix ones. ...
    (comp.lang.lisp)