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 address the string-port issue, though. Noah On Tue, Jun 5, 2012 at 5:31 AM, Daniel Krueger <keen...@googlemail.com> wrote: > 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 > %default-port-conversion-strategy and gives you the coding. In one > case you maybe rely on %default-port-conversion-strategy normally > being UTF-8 and then someone sets it to something else, which could > give some hard to track errors. I think explicity just makes code much > clearer and I think seperating textual and binary ports leads to more > explicity, that's my point of view.. > > WDYT? > > - Daniel >
