Hi Soeren,
On Tue, 2011-02-01 at 09:33 +0100, Soeren Moeller wrote:
Thank you for your answers, I will try both approces.
Oh - fun :-) is a complete expunging of the obsolete types not
possible ?
..
I very much hope it is possible, but tools/list is in the codebase
used for both classic list purposes and for situations where the
object is created once, is sorted, and then there is a lot of random
Ah - right :-) so, I suspect the common way to handle these is simply
to look around at the code accessing a given list, and consider how
frequently it is likely to be accessed. The std::vector also (kohei
suggested) is fast to append to if we do it carefully - so ...
Ultimately, run-time profiling will only show you what your data set
touches, and (as yet) we have no reliable set of representative calc
documents together to know what they look like ;-)
So - I would personally, just recommend converting them using a bit of
common sense / poking around to infer their use. We'll get performance
regression complaints later if we go too far wrong no doubt :-)
Thanks,
Michael.
--
michael.meeks@novell.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.