Changes to CodeCompletionWorker regarding multithreading

[David Nolden]

2011/1/18 Esben Mose Hansen <kde at mosehansen.dk>:
>
> Ah, not quite. There are two other cases for ABI-stability.
>
> There are packagers, which *needs* to have the SO-version correspond to a
> specific ABI. So every time you break ABI, you need to bumb the so number.
> They also worry that having 5 different apps depend on 5 different ABIs for
> one library will lead to excessive memory usage and odd dependency graphs.
>
> Then there are the library users. They need to be able to say to their
> downstream which version of your library to grab. And they would much prefer
> it if this is a version packed by their downstream's distribution.
> Constantly changing the ABI increases the risk that the version is not there
> yet/anymore.

Both of these points seem like they could be fixed by changed
workflows on the packager/distribution side (packers wouldn't need to
do more work, they would just need to have the right tools), and not
like general arguments for binary compatibility.

The fact that packagers don't seem to have the right tools makes this
a purely philosophical discussion though.

Greetings, David