Also be aware that this rope series is motivated by existing editors’ non-responsiveness with large files and long lines. The gap buffer article instead says
I’m not writing a string processing framework for managing gigabytes of data
the cost of moving the cursor is proportional to the distance that you move it
The gap buffer article doesn’t mention (handle?) unicode or non-printable character.
So, to me at least, it looks like ropes are a solution to all the gap buffer issues.
Very interesting series on using those data structures. Readers might also be interested in one that came as a counterpoint:
http://scienceblogs.com/goodmath/2009/02/18/gap-buffers-or-why-bother-with-1/
Also be aware that this rope series is motivated by existing editors’ non-responsiveness with large files and long lines. The gap buffer article instead says
The gap buffer article doesn’t mention (handle?) unicode or non-printable character.
So, to me at least, it looks like ropes are a solution to all the gap buffer issues.