> IMO our atomic data structure well deserves a container that fit our
> requirements as much as possible. I have argued thinking on edition
> (insert, cut, copy, paste, search, replace) that requires only standard
> STL iterator methods, and against unnecessary complexity.
I suddenly dawns on me that we might be misunderstanding each others:
I do not want to expose the complete string interface in the InsetChunk!
I want us to design our own minimal interface based on our own
iterators.
These iterators will expose exactly what is needed to do the editing
operations. And they will be polymorphic: They will function on both
InsetChunks, InsetParboxes, and all other insets, transparently.
The LString in the InsetChunk is private!
Greets,
Asger
