KConfigXT generated private members

[Aaron J. Seigo]

On Monday 30 May 2005 12:10, Duncan Mac-Vicar P. wrote:
> I noticed kconfig_compiler generates private members without a d-pointer
> (Private class). If I would need to expose a generated .h file as public
> api (for plugins) (it already supports adding visibility settings) it will
> be kinda hard to maintain BC when new settings are added.

an option to not inline the accessors in the header file would also be needed 
to protect against changes to the generated code from messing up source 
compat.

versioning of <entry>s so you can keep track of when something was added would 
also be nice. the rest could be up to the developer to ensure they don't 
remove / rename items to create a BIC interface.

> Is there any reason is was done this way, or adding this feature would be
> an enhancement?

i'm in want of these same things for libkicker.

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050530/7889aeae/attachment.sig>