seamless project model update
apaku at gmx.de
Tue Jul 13 21:17:29 UTC 2010
On 12.07.10 20:33:48, Andreas Pakulat wrote:
> On 12.07.10 13:08:25, Aleix Pol wrote:
> > On Mon, Jul 12, 2010 at 8:54 AM, Andreas Pakulat <apaku at gmx.de> wrote:
> > > On 12.07.10 04:46:26, Aleix Pol wrote:
> > > And last but not least: This doesn't make the model threadsafe at all,
> > > so IMHO this shouldn't be done as its confusing that one part makes an
> > > attempt to be threadsafe, but all others are still broken in that
> > > regard.
> > >
> > Hm...
> > Well, other options I can see are:
> > - To move this code to the CMake manager, but this will make its code to
> > change quite a lot
> > - Let the CMake tree as we had before
> > - make the rest of operations thread-friendly (not sure what would this look
> > like :/)
> That would be adding a lock to the item classes. However locking is a
> relatively expensive operation, so this might hit the performance of the
> tree for large tree's. Additionally I'm not quite sure wether adding
> locking to the items would be enough, could be its also necessary for
> the model itself. In that case you'd have a problem as we don't control
> all of the model code...
I've decided to have a try with that to see how much more complex the
code gets and how much the performance impact is. First step is pushed,
a small utility app that allows to easily do performance-checks on the
project model (at least I hope so).
Long life is in store for you.
More information about the KDevelop-devel