[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: [patch] request for review - apidox for kdelibs/kdeui (long)
From:       Brad Hards <bhards () bigpond ! net ! au>
Date:       2003-09-07 10:28:11
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, 07 Sep 2003 18:31 pm, Stephan Kulow wrote:
> Am Sunday 07 September 2003 08:46 schrieb Brad Hards:
> > There are four sorts of changes:
> > 1. #ifdef in some .cpp files to make the implementation match the
> > interface
>
> Definitly no way: you're removing functions.
OK, with a bit of help from frerich on #kde-devel, I now am clearer on what 
this does
I'm still a bit confused about the semantics of KDE_NO_COMPAT though. I see it 
being used in radically different ways across kdelibs/
If an application #defines KDE_NO_COMPAT, what is supposed to happen?

> > 3. Placeholders for the rest of the missing entries
>
> Definitly no way: if you want to fix doxygen warnings, document the
> functions, don't add placeholders.
I think this is a bit unreasonable, given the amount of code that doesn't have 
any parameter documentation. However I will either document it, or remove the 
changes.

Brad
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE/Wwg8W6pHgIdAuOMRAlakAJ99V/8V30YBCofF4UtWDJUJnCdCfACeKWLE
sktDoq7ertCttbjBrRyVbf8=
=QrXZ
-----END PGP SIGNATURE-----
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]