> > "BOOL -> bool" will cause problems. Memory usage for "new BOOL[n]", mixed > use with sal_Bool (pointers, references), the occasional "special" value > (SfxChildWinInfo::bVisible). Shouldn't we go the safe way and change BOOL to > sal_Bool instead?
I agree with you Niklas. It will be much better/safer to change FASTBOOL to sal_Bool. Does sal_Bool(unsigned char) is slower than FASTBOOL (int)? It could make OpenOffice.org code slower if it will call functions with bool parameters a lot. I don't want to loose the performance, see: http://cboard.cprogramming.com/cplusplus-programming/119320-bool-vs-int-faster.html Regards Bartosz --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
