#include <QFoo>

[Thomas Zander]

On Thursday 27 July 2006 23:46, Allen Winter wrote:
> (for some reason I'm not following Thiago's posting these days.
> the one in the KDE_EXPORT thread the other day hurt my brain)

Heh, it took me several readings as well; my guess is that speaking French 
too much where they reverse lots of concepts is bad for your (short term) 
reasoning ;)

Let me try;  There are:
1) classes that are exported and public
2) classes that are not exported and not public
3) classes that are exported and not public

The only other option (not exported and public) i'll number (4), can not 
exist since code would not compile if the programmer would incidently 
mark it as such while one of the others were intended.

1 implies the programmer added a EXPORT
2 is marked as @internal
3 is marked @internal and has an EXPORT (and is a hack)

And nr 4 is the whole point, since that is the one case your suggestion 
would try to solve. But it is already solved by the fact that we will get 
a linking error if we forgot a EXPORT like macro.
For example when we use that class from the (mandatory) unit test.

-- 
Thomas Zander
-------------- 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/20060728/6be4e5b5/attachment.sig>