Le 01/08/2009 18:29, Abdelrazak Younes a écrit :
In case this question was left unanswered, we don't want a buffer_ member in InsetMathChar because this sucks 4 bytes of memory for each inset. And, AFAICS, there's no need to access the Buffer in an InsetMathChar.
First, removing a setBuffer method does not change the fact that Inset has a buffer_ member.
Moreover, as Vincent the buffer_ member will probably come handy when we have change tracking in math. How much memory does an InsetMathChar use these days? The fact that this member was added by andré, who was also the keeper of Inset virginity (in some way :) tells me that the problem may not really exist. All I did was to push forward the logic of a change that was only half done. I think that having access to the inset buffer is a great win, especially for inset layouts JMarc
