On 08 Jul 2001 00:01:31 +1000, Martin Sevior wrote:
>
> Very interesting! I'd like to trace through to find the cause of this but
> Joaquin's right. This is the safe thing to do and add very little overhead
> to the method. Please do this.
gook luck! ;-)
> > PS: Can we erase "void cleanFragsConst() const" and the utility method
> > that is just above this one, make pf_Fragments::m_vecFrags,
> > pf_Fragments::m_pLastFragClean & pf_Frag::m_docPos mutable and turn
> > "void pf_Fragments::cleanFrags(pf_Frag*)" & "void
> > pf_Frags::setPos(PT_DocPosition)" into const method's, please (all these
> > variables are only there to cache values, so imo a change in these
> > variables don't change the logical state of the related objects)?
> >
>
> I think so. I just learnt about mutable member variables. I don't know if
> these are allowed within the AbiWord C++ guidelines. I do know that
yup. I think that I used it several months ago and nobody complained
:-) in addition, I've seen it used occasionally before I used it.
Cheers,
--
Joaqu�n Cuenca Abela
[EMAIL PROTECTED]
