Matúš Kukan 0c24faee6b FastSerializer: Also use cache for writing to ForMerge if we are inside mark() ...

To ensure the correct order of calling ForMerge methods,
call flush always before touching maMarkStack.

This was the missing piece in optimizing write() methods,
because of writeBytes() checking each time what to call.
E.g. for Calc documents we don't use maMarkStack at all.
So, just transfer the output to proper "ForMerge" when inside mark()
and allow optimizations.
This commit makes write() methods almost 1/3 as fast.

Change-Id: I96c13888206c81f87e29b998839f78ea9d5570af

2014-10-23 14:30:29 +02:00

..

expatwrap

More -Werror,-Wunused-private-field

2014-10-15 15:58:56 +02:00

fastparser

fastparser: avoid allocating un-used FastTokenLookup class.

2014-10-23 11:53:17 +02:00

tools

FastSerializer: Also use cache for writing to ForMerge if we are inside mark()

2014-10-23 14:30:29 +02:00