Email list hosting service & mailing list manager


STANDARD-INPUT-PORT vs. STANDARD-INPUT-STREAM [was: Specification vs. Implementation] Michael Sperber 24 Aug 2005 20:10 UTC

Alex Shinn <xxxxxx@gmail.com> writes:

> This means the standard procedures for creating ports are allowed to
> return ports based on the underlying I/O libraries with no relation to
> the SRFI-68 streams or readers/writers.  There are still some
> ambiguities though, since we have both STANDARD-INPUT-PORT and
> STANDARD-INPUT-STREAM, and it's not clear what the relation between them
> is and what happens if you use both.

I suppose this could be tied down more, but given the vagueness of the
notion of "stdin" in general, I'm unsure this would be very useful.
Do you you have any suggestions?

--
Cheers =8-} Mike
Friede, Völkerverständigung und überhaupt blabla