Andy Wingo scripsit:

> I would like to second the concern about calling mixed binary and
> character IO procedures on a port.

This needs to be rethought, and I'm hoping to get a chance to rethink
it.

> Also, the spec should clarify which ports are (typically) character
> ports, besides string ports.

Ticket already filed.

> The FILE-SPEC stuff makes me uneasy.  Where does it come from?  It's
> certainly not the standard practice in any implementation I'm familiar
> with.

It's a variant of Gambit-C and SRFI 91, using p-lists instead of keyword
arguments.  It has the advantage that you can add more features to the
various file openers without adding more and more procedures to handle
them, or having to open them and then use various setters which can
potentially be called at any time.

> Also, there are no examples of FILE-SPEC.

Editorial ticket filed.

> Also there is the /settings list/ definition, which is never used
> anywhere.

Changed to file-spec.

--
My confusion is rapidly waxing          John Cowan
For XML Schema's too taxing:            cowan@ccil.org
    I'd use DTDs                        http://www.ccil.org/~cowan
    If they had local trees --
I think I best switch to RELAX NG.

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