> On May 4, 2015, at 3:21 AM, Tamas Papp <tkp...@gmail.com> wrote: > > I think you misunderstand: IOBuffer is suggested not for mutable string > operations in general, but only for efficient concatenation of many > strings. > > Best, > > Tamas
I don’t think that I misunderstood - it’s that using IOBuffer is the only solution that has been given here… and it doesn’t handle what I need to do efficiently... If you have a better solution, please let me know… Scott > On Mon, May 04 2015, Scott Jones <scott.paul.jo...@gmail.com > <mailto:scott.paul.jo...@gmail.com>> wrote: > >> I wasn't trying to say that it was specific to strings, I was saying that >> it is not specific to I/O, which the name would seem to indicate... >> and it keeps getting brought up as something that should be used for basic >> mutable string operations. >> >> On Sunday, May 3, 2015 at 3:20:43 PM UTC-4, Tamas Papp wrote: >>> >>> consider >>> >>> let io = IOBuffer() >>> write(io,rand(10)) >>> takebuf_array(io) >>> end >>> >>> IOBuffer() is not specific to strings at all. >>> >>> Best, >>> >>> Tamas >>> >>> On Sun, May 03 2015, Scott Jones <scott.pa...@gmail.com <http://gmail.com/> >>> <javascript:>> >>> wrote: >>> >>>> Because you can have binary strings and text strings... there is even a >>>> special literal for binary strings... >>>> b"\xffThis is a binary\x01\string" >>>> "This is a \u307 text string" >>>> >>>> Calling it an IOBuffer makes it sound like it is specific to I/O, not >>> just >>>> strings (binary or text) that you might never do I/O on... >>>> >>>> On Sunday, May 3, 2015 at 2:43:14 PM UTC-4, Kristoffer Carlsson wrote: >>>>> >>>>> Why should it be called StringBuffer when another common use of it is >>> to >>>>> write raw binary data?
