There can be only one! (global.h)

[Peter Kümmel]

David Faure wrote:
> On Monday 06 March 2006 12:34, Peter Kümmel wrote:
>> So what's the whole problem renaming some files?
> 
> The problem IMHO is that #include <kio/kio-global.h> looks redundant.

The first argument that could stop me posting to this thread. :)

> Remember that many apps include it, this isn't only internal to kio.
> So why should internal kdelibs compiling issues force apps to write an
> ugly include statement? #include <kio/global.h> is what was intended,
> and it should just work that way.

Is kio/global.h that useful that it will be included without any other
headers of kio? I just don't know.

> So what's the problem with declaring the problem fixed and moving on? ;-))

I've the impression it's not a good fix.

And I've watched too often Highlander. :)

> It's good that a bug in the include paths was noticed; I actually think there is
> more cleanup to do on the include paths, as I posted earlier on, but I'll have
> to wait for cmake-kde to include the "auto include current dir" feature.
>