Hello CLISP crew!
This is not really a bug. After all, Cygwin just started supporting named pipes. It appears, though, that the build of CLISP being distributed along with Cygwin doesn't recognize them. The version of CLISP is this:
Welcome to GNU CLISP 2.48 (2009-07-28)
Since CLISP is turrning out to be the most comfy place for my artificial intelligence to, well... think.
The behavior I noticed is that CLISP would just lock when trying to write to a pipe. Writing to files works fine. Reading from the pipe in another terminal window invoked an error in the CLISP session.
I'll mention this to the Cygwin guys too. I just want you to be on the same page.
Thanks for all the help.