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

On 6/15/06, Anselm Heaton <anselm / netuxo.co.uk> wrote:
>
> > Matz has said several times that he will maximize the breakage moving
> > to Ruby 2.0.
>
> 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.
>
>

Will you volunteer to go throughout all source code of Ruby core library
(about 350 KSLOC of C and Ruby), inspect, fix and test all the consequent
issues? How long time could it take? :)

------art_93289_30409874.1150366227811--