Re: binary file upload with CLISP

[David T. <dv...@da...>]

> Yes. And this is needed to ensure that after clisp terminated, the next
> prompt comes in a fresh line or, if the output went to a file, the last
> line of the file is correctly terminated. In your case, you will 
> probably
> need to call FRESH-LINE on the output stream before you switch it to
> binary, if you want no newline after the binary part.

Hi Bruno,

under Mac OS X I cannot 'switch to binary', /dev/stdout is locked (by 
setting it to ------) once it is open, and when I close 
*standard-output* from CLISP, I cannot re-open it. But let's leave this 
issue alone; I am not going to convince you that there is indeed a 
character with code 13 in Latin-1 encoding.

I just want to send as many characters (well, bytes in fact, but let's 
assume they are characters) to the output stream, no more, no less. 
This should not be different from closing any file. When I close a 
file, CLISP (as well as any other lisp implementation available to me) 
does not fresh-line it.

Where in the standard it is written that the last line to 
*standard-output* (redirected to a pipe going to a browser through an 
http server) must be properly terminated by calling fresh-line? I just 
want to get what I asked to.

I just don't want any program to do things I didn't ask it to. (That's 
why I don't use Emacs, by the way).

David