On Fri, 26 Mar 1999, Asger Alstrup Nielsen wrote:
> The LString in the InsetChunk is private!
Then, as I suspected from the beginig, all the set of methods from LString
won't be used.
Let's analize the use cases of the chunk container to see what is
suitable:
1- Editing, only iterator methods are needed.
2. Rendering. It's more efficient that each chunk return a C string
than rendering in one char basis. Here btw appear our already
discussed problem of the 3 rectangle shape chunk, as you called
it (so in the worst case we would need one C string per row.) Any
container that can return a C string from its contents is good
in this case.
3. Writing. We never write a chunk directly to disk, currently we're using
an LString as writting buffer. Anyway sending a C string instead of
one char each time improves performance but it's not much relevant
since the slow process would be to write directly on disc.
Again any container able to return a C string is ok.
4. Reading. The parsing use to be in a char or word basis anyway. If
we get some way we can feed new chunks with entire C strings, that
would improve performance a bit, but again, we are not reading
directly from disc. Those strings would be already in the parser
buffer.
Am I forgetting anything?
Alejandro
