30 Apr
2004
30 Apr
'04
6:51 a.m.
Lars Magne Ingebrigtsen larsi@gnus.org writes:
which fixes the problem. But surely this isn't supposed to be necessary.
IMHO, flushing is the responsibility of the stream user.
Lispworks has a stream:stream-soft-force-output function. It's not documented, but I assume this is called when Lisp is idle. I added methods for comm:socket-stream and our custom output streams. This seems to solve the problem. Let's hope those methods don't infer with application code.
Helmut.