I think there is another problem, which is not string-port-specific,
but touches on it:
Can open-string-input-port and open-string-output-port be
implemented using only public library functions? This is
important, IMO. There is a make-custom-binary-input-port,
but I don't see a make-custom-textual-input-port. Can the
latter be implemented sanely on top of the former? I suppose
it could in theory, but it seems very wrong.
It should be possible to implement transcoded-port (or something
with very similar effect) using make-custom-textual-input-port
and make-custom-textual-output-port.
--
--Per Bothner
per_at_bothner.com http://per.bothner.com/
Received on Mon Jan 22 2007 - 13:12:27 UTC