Vincent Manis scripsit:

> I'd therefore suggest adding a procedure named make-eof-object or some such, and defined to return one of the set of eof objects for the implementation.

Ticket #337 filed.

> 2. I'm not sure I understand the difference between `input port'
> and `port capable of doing input operations'. The draft offers
> input-port? and output-port? that are true if the argument is an
> input (or output port). Yet close-input-port and close-output-port
> are clearly defined to shut down the input or output side of a port,
> leaving the other side still functioning, and explicitly work on things
> that are not input (or output) ports.

There isn't intended to be a difference.  Editorial ticket #338 filed.

--
John Cowan              http://www.ccil.org/~cowan      cowan@ccil.org
"After all, would you consider a man without honor wealthy, even if his
Dinar laid end to end would reach from here to the Temple of Toplat?"
"No, I wouldn't", the beggar replied.  "Why is that?" the Master asked.
"A Dinar doesn't go very far these days, Master.        --Kehlog Albran
Besides, the Temple of Toplat is across the street."      The Profit

_______________________________________________
Scheme-reports mailing list
Scheme-reports@scheme-reports.org
http://lists.scheme-reports.org/cgi-bin/mailman/listinfo/scheme-reports