Hey,
I think if you only use them seperate there's a clearer distinction.
If you have it mixed you can do some, say hacking, where you see it
works but you can't see anywhere what you're exactly doing, most of it
is hidden in the guile implementation, which interprets
I agree that separate binary and textual ports are cleaner, but what
about using a port to deal with a mixed binary/textual protocol, like
HTTP? I think the cleanest way to deal with that would be to have a
port where you first read characters and then read binary data.
That doesn't directly
Hi,
Daniel Krueger keen...@googlemail.com skribis:
If you have it mixed you can do some, say hacking, where you see it
works but you can't see anywhere what you're exactly doing, most of it
is hidden in the guile implementation, which interprets
%default-port-conversion-strategy and gives
Hi!
Noah Lavine noah.b.lav...@gmail.com skribis:
I agree that separate binary and textual ports are cleaner, but what
about using a port to deal with a mixed binary/textual protocol, like
HTTP? I think the cleanest way to deal with that would be to have a
port where you first read characters
Hi,
Daniel Krueger keen...@googlemail.com skribis:
In the first place I agree that ports should be seperated and not
mixed textual/binary
Why?
(I understand how this would work in terms of APIs co., I’m just
unsure what the rationale is.)
Thanks,
Ludo’.