KDE_NO_COMPAT

[Andrew Coles]

On Thursday 10 Jun 2004 12:11, Stephan Kulow wrote:
> It's not too easy as you might break binary compatability depending on this
> define.

Ah, that's true.  Looking at kaction.h it is only applied to methods occuring 
at the end of the header file (so the addresses of the non-deprecated 
functions are the same irrespective of whether KDE_NO_COMPAT is set or not) 
or to those which are defined in the header file (and hence have to be 
inlined, so have no address, if I understand correctly).

So if these two rules are obeyed can it be done safely?

Andrew