From kde-core-devel  Tue Feb 14 21:07:11 2006
From: Adriaan de Groot <groot () kde ! org>
Date: Tue, 14 Feb 2006 21:07:11 +0000
To: kde-core-devel
Subject: kconfigbase parameter names
Message-Id: <200602142207.11955.groot () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113995124414001
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2807115.M1W53c6k05"

--nextPart2807115.M1W53c6k05
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

In kconfigbase.h, there are parameters that are name pValue or rValue (for =
the=20
write methods, mostly). It seems to be random (I can imagine that they mean=
=20
pointer and reference, respectively, but that doesn't match the usage). Is=
=20
there any semantics to the naming or can this uniformly be changed to=20
"value" ? That would fix a half-dozen @copydoc-related APIDOX errors in one=
=20
go.

=2D-=20
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot

--nextPart2807115.M1W53c6k05
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (FreeBSD)

iD8DBQBD8kZ/dqzuAf6io/4RAl9MAJ95ARo8QqZ/bFr0RA9cIdxrHs+KyQCfQvik
zjutqAvRQhruWJZDf3KYh10=
=LhNh
-----END PGP SIGNATURE-----

--nextPart2807115.M1W53c6k05--