------art_5807_17075514.1150366207325
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi!

If that is the case, is there a reason why we should continue using String
> for
> bytes then ? We could have a ByteBuffer class or something similar. IO
> objects would return ByteBuffer ; ByteBuffer.to_s would return the string
> equivalent in the current encoding, and ByteBuffer.to_s('my encoding')
> into
> the required encoding.


+1, that would be very nice. In some other platforms (like java or .net),
the programmer doesn't know about the bytes (only length in terms of chars)
unless he's willing to digg into them (using a specific class).

--
Thibaut

------art_5807_17075514.1150366207325--