[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-optimize
Subject:    Re: Fwd: Re: Fwd: Re: [PATCH] libkdeinit symbol pruning
From:       Karl Vogel <karl.vogel () seagha ! com>
Date:       2004-07-21 12:10:54
Message-ID: 200407211410.55199.karl.vogel () seagha ! com
[Download RAW message or body]

André Wöbbeking wrote:

> On Wednesday 21 July 2004 13:38, Karl Vogel wrote:
>>
>> It's the other way round.. the gcc visibility patch enables you to
>> hide everything by default, so that you only need to add an export to
>> the stuff you really want exported.
> 
> I read it but this way you've to mark every public method, haven't you?

Yups.. that's correct. That's also why I first had a go at it with QT, as they 
already did that (since it's required on windows).

> I don't understand why invisibility isn't the default (at least per
> command line option) for private class member and things declared in
> CPPs.

Well I wondered about that too.. so I put the question to the gcc-devel 
mailinglist:

"
Inline member functions have access to these private members and might
be compiled into application code.
"
--  http://article.gmane.org/gmane.comp.gcc.devel/51576

_______________________________________________
Kde-optimize mailing list
Kde-optimize@kde.org
https://mail.kde.org/mailman/listinfo/kde-optimize

[prev in list] [next in list] [prev in thread] [next in thread]