A Web-based News Reader
| Subject | Re: Transcoding - who's doing what? |
| From | Ben Hinkle <bhinkle4@juno.com> |
| Date | Tue, 17 Aug 2004 08:35:25 -0400 |
| Newsgroups | digitalmars.D |
> (3) /This is most important/. In the typical scenario, the caller will be > reading bytes from some source - which /could/ be a stream - and will want > to get a single dchar. We're talking about a "get the next Unicode > character" function, which is about as low level as it gets (in terms of > functionality). But you can't build such a function out of your string > routines, because you have no way of knowing in advance how many bytes > will need to be consumed from the stream in order to build one character. > So what do you do? Read too many and then put some back? Not all byte > sources will allow you to "put back" or "unconsume" bytes. std.stream supports ungetc, which pushes a character back by maintaining an array of pushed-back characters. Right now only the text functions check this array for content, though. I think the idea was that if one is storing text and binary data mixed together that the text are stored with writeString which puts a length byte followed by the text. | |
