On Tuesday 09 September 2003 11:52, Brad Hards wrote:
> On Tue, 09 Sep 2003 11:20 am, Nicolas Goutte wrote:
> > Sorry to having made a confusion! It is the other way round. Of course, you
> > define KDE_NO_COMPAT in a program only when you do *not* want
> > compatibility. You make sure that it is not defined if you want
> > compatibility to the previous major version.
> OK, so #define KDE_NO_COMPAT only ever removes compatibility code.
> 
> In that case, wouldn't it make more sense not to define KDE_NO_COMPAT when
> building the documentation:
[patch]

This would make all the deprecated API calls invisible to doxygen and you have no
way to document it.

> 
> In any case, we should document @deprecate'd API elements with at least the
> replacement code.

That's done as far as I can see.

Greetings, Stephan

-- 
There may be no I in TEAM, but a M and an E.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<