From kde-devel Tue Sep 09 09:52:07 2003 From: Brad Hards Date: Tue, 09 Sep 2003 09:52:07 +0000 To: kde-devel Subject: Re: [patch] request for review - apidox for kdelibs/kdeui (long) X-MARC-Message: https://marc.info/?l=kde-devel&m=106310156805465 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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: Index: Doxyfile.global =================================================================== RCS file: /home/kde/kde-common/admin/Doxyfile.global,v retrieving revision 1.17 diff -u -4 -p -r1.17 Doxyfile.global - --- Doxyfile.global 21 Aug 2003 09:46:11 -0000 1.17 +++ Doxyfile.global 9 Sep 2003 09:33:37 -0000 @@ -875,9 +875,9 @@ INCLUDE_FILE_PATTERNS = # gcc). The argument of the tag is a list of macros of the form: name # or name=definition (no spaces). If the definition and the = are # omitted =1 is assumed. - -PREDEFINED = QT_VERSION=320 __cplusplus KDE_NO_COMPAT +PREDEFINED = QT_VERSION=320 __cplusplus # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then # this tag can be used to specify a list of macro names that should be expanded. # The macro definition that is found in the sources will be used. In any case, we should document @deprecate'd API elements with at least the replacement code. Brad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE/XaLIW6pHgIdAuOMRAo4QAJ9/LPKNooKY9GJ6hrWIQxcqsIZ/yQCfXZ4L 5hf32GGDoJRZ1hSrDOX6VSc= =+89G -----END PGP SIGNATURE----- >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<