KDE_NO_EXPORT

[Thiago Macieira]

Allen Winter wrote:
>It seems to me that public library classes should either be KDE_EXPORTed
> or KDE_NO_EXPORTed. True?

Not exactly. They should be XXXXX_EXPORT'ed when they are public. There's 
no need to no-export private ones.

KDE_EXPORT should never be used directly.

>So, what I'm really asking is... for public classes that are not marked
> with the FOO_EXPORT macro, would it be ok to mark them with the
> KDE_NO_EXPORT macro?  (assuming that they really are not for exporting
> and we simply didn't forget to FOO_EXPORT them).

That's unnecessary cruft in our headers. No compiler requires that flag.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- 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/20060718/e22a06bc/attachment.sig>