From: Yukihiro Matsumoto <matz@...>
Date: 2009-02-04T09:38:17+09:00
Subject: [ruby-core:21818] Re: [Feature #908] Should be an easy way of reading 	N characters from am I/O stream

Hi,

In message "Re: [ruby-core:21817] Re: [Feature #908] Should be an easy way of reading 	N characters from am I/O stream"
    on Wed, 4 Feb 2009 09:33:44 +0900, Michal Suchanek <hramrach@centrum.cz> writes:

|>  Re: seeking by character count - it would be nice, but I have no idea how it could be implemented efficiently!
|
|For UTF-8/UTF-16/SJIS/EUC-JP/BIG5 .. no. UTF-32 is dword aligned but
|you cannot tell what byte ordering it uses reliably. Bad thing. Seeks
|are probably not for text files or only for text files you have parsed
|already so you know where you are seeking.

Right.  Hence I reject the character based seek.  Thank you.

Regarding the original N character read, I am positive, but still
haven't decided yet for API.

							matz.