Andre Poenitz wrote: > The obvious idea is to use and/or cache some ParagraphList iterator > instead of the par offset... > > Maybe we've to use both. In fact, it's almost the same as with the > 'inset_' member: This is just a form of a cache itself.
Right. > So we'd remove the 'paroffset_type & CursorSlice::par()' member and > provide 'elementary' accessors > > setFirstPar() > setLastPar() > incrementPar() > > etc. Doesn't sound overly complicated... Can you explain a bit more? You store both a ParagraphList::iterator pit_ and the offset. Then you use only pit_ for iterating? Doesn't that defeat the purpose of having the offset at all (hum... what was it again)? Alfredo
