KDE_NO_EXPORT

[Thomas Zander]

On Monday 17 July 2006 17:01, Allen Winter wrote:
> It seems to me that public library classes should either be
> KDE_EXPORTed or KDE_NO_EXPORTed. True?

If there is a class in kdelibs that is not _used_ by a class outside that 
same library, but should have had the EXPORT macro, then something is 
wrong and it should either not be in kdelibs or it should indeed not be 
exported.
This means that in practice its unneeded to have this NO_EXPORT as 
forgetting the export will very quickly make a compile (elsewhere) fail.

Because of that, I personally see no advantage in having this, and I think 
the only result is more work and hard to track down copy-paste errors.
-- 
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/20060717/10c724f0/attachment.sig>