[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IO redirection in Elisp
- To: Ellis
- Subject: Re: IO redirection in Elisp
- From: John C Ruttenberg <Ruttenberg>
- Date: Tue ,18 Oct 83 17:07:16 EDT
- Cc: Fisher
- In-reply-to: John R Ellis <Ellis>, Tue, 18 Oct 83 15:56:26 EDT
- Resent-date: Tue, 18 Oct 83 17:41:28 EDT
- Resent-from: John R Ellis <Ellis@YALE.ARPA>
- Resent-to: T-Discussion@YALE.ARPA
In-Reply-To: John C Ruttenberg <Ruttenberg>, Tue, 18 Oct 83 07:03:08 EDT
You should resend your message to T-DISCUSSION.
If you still have a copy of this message, please resend it for me. I
didn't keep a copy.
I think these hacks are more to the point in Elisp where you have to
open a channel and then select it. In Maclisp, for example, you could do:
(iota ( (standard-output "temp:junk.junk"))
to get the effect of
(iota ( (file "temp:junk.junk") ) (without file
Except that each IO statement made its own decision as to where it was
going to write. So there was a greater chance of it not working.
I like the effect you get on UNIX and in the TOOLS programs. It's so
easy to write to standard output (as opposed to anywhere else) that you
nearly always do it. But writing to standard-error is almost as
easy, so few programs fail to write their errors there. Interesting to
see that Maclisp, whose IO system strongly resembles that of the
UNIX and TOOLS runtims misses this effect badly. While Elisp, whose
IO model is so different seems to hit the nail on the head.