[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
print question
- To: edsel!bhopal!jonl@navajo.stanford.edu
- Subject: print question
- From: Don Morrison <dfm@jasper.palladian.com>
- Date: Mon, 29 Jun 87 12:56 EDT
- Cc: navajo!sandra%orion%cs.utah.edu@navajo.stanford.edu, navajo!common-lisp%sail.stanford.edu@navajo.stanford.edu
- In-reply-to: <8706281227.AA00660@bhopal.edsel.uucp>
- Reply-to: Don Morrison <DFM%JASPER@live-oak.lcs.mit.edu>
Date: Sun, 28 Jun 87 05:27:40 PDT
From: edsel!bhopal!jonl@navajo.stanford.edu (Jon L White)
Although the MacLisp printer took care to insert "newline"'s ocasionally,
I finally came to believe that PRINT was the wrong place to handle this.
I would think that it does need to be handled higher up than character I/O. I
would expect newlines to replace spaces between tokens, but not spaces embedded
within tokens, such as strings; otherwise you can't parse what you print. Or am
I missing something?
- References:
- print question
- From: edsel!bhopal!jonl@navajo.stanford.edu (Jon L White)