optimizing & api-doc

[Michael Olbrich]

Hi,

I've followed the discussion here quite some time now, and I'm missing
the kde related parts a bit. It's kde-optimize after all. I know there
are issues with the linker etc. but we can't to much about that. And I
think we have better things to do here, than discussing which hack
improves the situation most. These hacks may help us, but not those who
need a stable environement, or don't have the time/knowlede to use them.

>From what I've seen, many speed problems within c++ programs have their
origin in the language. In c++ it's easy to hide complexity. This helps
to have a clean design, and makes the developers productive. But the
complexity is still there and can make the programs slow. 

So what I'm missing here, and this is true for both, kde and qt api
documentation, are hints about the complexity of methods, etc. e.g. mark
methods, that shouldn't be called to often, or when overloading a
function, which one is fast, which is slow. QString::find comes to my
mind here.

I think, things like this can help writing faster code while keeping it
simple and clean.


Michael