[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
New Issue: WRITE-NEWLINE
- To: KOSCHMANN@SUMEX-AIM.Stanford.EDU
- Subject: New Issue: WRITE-NEWLINE
- From: Kent M Pitman <KMP@STONY-BROOK.SCRC.Symbolics.COM>
- Date: Fri, 21 Oct 88 12:27 EDT
- Cc: CL-Cleanup@SAIL.Stanford.EDU
- In-reply-to: <12440047204.16.KOSCHMANN@SUMEX-AIM.Stanford.EDU>
The functionality you're requesting is not a duplication of what
PRINT does. Print prints a newline before AND a space after. I don't
think anyone's going to buy doing (WRITE frob :NEWLINE-BEFORE-AND-SPACE-AFTER T)
nor even (WRITE frob :NEWLINE-FIRST T :SPACE-AFTER T).
In practice, most programmers don't even use WRITE (probably for fear
that the keyword argument deciphering is going to be too inefficient)
and I suspect that the designers would be more likely to consider a
request to flush WRITE than to extend it. If you want a general purpose
I/O operator, FORMAT is probably a better candidate.
Anyway, regarding your test case:
(dotimes (index 4)
(write index :newline))
0
1
2
3
NIL
I assume you meant :NEWLINE T, since keywords must have accompanying values.
I don't think it's unreasonable for us to ask you to do the following, which
is available now:
(dotimes (index 4)
(write #\Newline :escape nil)
(write index))