Suggested KDEPrintInternal namespace

Alex Merry huntedhacker at
Mon Sep 10 12:40:16 BST 2007

On Tuesday 04 Sep 2007, Alex Merry wrote:
> It has been mentioned before that KDEPrint pollutes the global
> namespace extensively with many classes that do not begin with K. 
> What's more, these are almost all internal to KDEPrint, have no
> binary compatibility guarantee and are used only by the KDEPrint
> management module in kdebase (which is why there are exported).
> It would be good to put all the internal stuff in its own namespace.

> 2. Leave the public classes alone, and put the internal things in a
> KDEPrintInternal namespace (or KPrintInternal...)

Yeah, this isn't happening, sorry.  It's driving me insane, and I've 
only made it through libkdeprint itself (ie: I haven't made anything 
else build with it yet).


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <>

More information about the kde-core-devel mailing list