Re: [Libreoffice-commits] core.git: include/svl sc/source solenv/gdb svl/qa svl/source svx/source sw/source

On 2017/01/20 8:30 PM, Eike Rathke wrote: commit 2757ee9fe610e253e4ccc37423fa420004d0f388 used std::map in SfxItemSet I suspect that introduced some performance drawback, which can be seen Could you check if there are optimizations possible now that std::map is used? I had a look,

[Libreoffice-commits] core.git: include/svl sc/source solenv/gdb svl/qa svl/source svx/source sw/source

include/svl/itemiter.hxx| 32 - include/svl/itemset.hxx | 10 sc/source/core/data/patattr.cxx |6 solenv/gdb/libreoffice/svl.py | 44 + svl/qa/unit/items/test_itempool.cxx | 55 - svl/source/items/itemiter.cxx | 62 +-

Re: [Libreoffice-commits] core.git: include/svl sc/source solenv/gdb svl/qa svl/source svx/source sw/source

Hi Noel, On Tuesday, 2017-01-17 08:08:08 +, Noel Grandin wrote: > commit 2757ee9fe610e253e4ccc37423fa420004d0f388 > Author: Noel Grandin > Date: Mon Jan 9 10:27:22 2017 +0200 > > used std::map in SfxItemSet > > instead of naked array I suspect

[Libreoffice-commits] core.git: include/svl sc/source solenv/gdb svl/qa svl/source svx/source sw/source

include/svl/itemiter.hxx| 32 - include/svl/itemset.hxx | 10 sc/source/core/data/patattr.cxx |6 solenv/gdb/libreoffice/svl.py | 44 - svl/qa/unit/items/test_itempool.cxx | 54 + svl/source/items/itemiter.cxx | 62 +-