On Fri, Oct 31, 2003 at 11:14:14AM +0100, Alfredo Braunstein wrote:
> Angus Leeming wrote:
>
> >> hasParagraphs is never used in the code, and we need numParagraphs
> >> for having PosIterator/Cursor::operator--
> >
> > Who could possibly object? Go for it.
>
> The ways of objections are misteri
Angus Leeming wrote:
> Alfredo Braunstein wrote:
>> [Btw, it should be super easy to implement regex searches right? It
>> [would
>> suffice to implement operator* that gives pit->getChar(pos) if pos <
>> size and some '\n' if pos == size. In that way one could also search
>> for newlines etc. Met
Alfredo Braunstein wrote:
> [Btw, it should be super easy to implement regex searches right? It
> [would
> suffice to implement operator* that gives pit->getChar(pos) if pos <
> size and some '\n' if pos == size. In that way one could also search
> for newlines etc. Methink.]
Great idea.
... it w
Angus Leeming wrote:
>> hasParagraphs is never used in the code, and we need numParagraphs
>> for having PosIterator/Cursor::operator--
>
> Who could possibly object? Go for it.
The ways of objections are misterious... ;-) I'll do it then.
>> PS: should I drop PosIterator and try to make Cursor
Alfredo Braunstein wrote:
> Can I do it?
>
> hasParagraphs is never used in the code, and we need numParagraphs
> for having PosIterator/Cursor::operator--
Who could possibly object? Go for it.
> PS: should I drop PosIterator and try to make Cursor::operator++/--
> operative?
Why not make PosIt
Can I do it?
hasParagraphs is never used in the code, and we need numParagraphs for
having PosIterator/Cursor::operator--
PS: should I drop PosIterator and try to make Cursor::operator++/--
operative?
Alfredo
