[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Requests for clarification
- To: common-lisp@SU-AI.ARPA
- Subject: Requests for clarification
- From: STEELE@TL-20A.ARPA
- Date: Tue 14 Aug 84 13:54:45-EDT
The following requests for clarification were received from
a few people at Data General:
For a stream constructed with make-two-way-stream, what is the result
of applying stream-element-type to the stream, especially if the
element-types of the two underlying streams are different?
Under make-concatenated-stream, it should be made clear (if it is indeed
the case) that the resulting stream delivers to its clients only one
eof, after the contents of all the subsidiary streams have been
deleivered; the eofs from all but the last stream are not delivered.
How does the close function operate on various non-primitive streams?
For example, does close of a two-way stream close the two underlying
streams? What about close of a concatenated stream?
As a concatenated stream hits eof on each subsidiary stream, are those
subsidiary streams closed?
Some statement about "constant" list structures in compiled code
needs to be made. Many implementations would like to place constant
list structure, particularly constants in compiled code, in read-only
memory. (MacLISP does this.) This would mean that an expression such
as (nconc '(a b c) x) would be illegal, at least in a program to be
An explicit statement should be made as to how equal and equalp treat
structures. DO structures fall under the general heading of "objects
that have components"?