|
From: | Dan Muresan |
Subject: | [Chicken-users] Re: stream API (was busy-wait in tcp-connect) |
Date: | Wed, 23 May 2007 19:43:12 +0300 |
User-agent: | Thunderbird 1.5.0.10 (X11/20070306) |
Not sure what you mean. As opposed to text streams?
Binary streams as in binary data, as opposed to text.
Calling read-char repeatedly is probably not efficient; besides, read-char may not be the same as read-byte (if utf8 is loaded).Actually 'read-byte' uses the builtin 'read-char' when the utf8 egg is loaded. I was wrong about ##sys#custom-*-port not working w/ UTF8, at least in the broader sense. Excellent.
1. I can't find the documentation for read-byte. I didn't even realize that read-byte existed. What i meant was that read-char might read multiple bytes, when the programmer wanted to read a single byte of binary data.
2. You did not address the other point -- calling read-char repeatedly is probably not efficient. I think being able to read binary data efficiently is mandatory for a language that's supposed to be practical, no?
Best, Dan
[Prev in Thread] | Current Thread | [Next in Thread] |