This is the mail archive of the
mailing list for the GCC project.
Re: gcc visibility used by moz
- From: Daniel Jacobowitz <drow at false dot org>
- To: Tristan Wibberley <maihem at maihem dot org>
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 11 Jul 2006 22:39:43 -0400
- Subject: Re: gcc visibility used by moz
- References: <44B412CC.firstname.lastname@example.org> <44B41C1A.email@example.com> <44B44AA5.firstname.lastname@example.org>
On Wed, Jul 12, 2006 at 02:04:37AM +0100, Tristan Wibberley wrote:
> If the programmer had intended that the type should appear to not exist.
> it wouldn't be defined in a header #include-able by client code. The
GCC doesn't know if the header is includable by client code; I assume
that's the use Jason intended for marking classes hidden ("it belongs
to this shared object and no one else can see it").
> In the examples above, client code that knows (via headers) that the
> classes exist should be able to get pointers to instances via exported
> functions, access any visible or virtual members, and pass the pointers
> back into visible functions of the shared object - or even dereference
> the pointers to pass by reference.
So... what does it restrict, then? Is it just defaulting methods to
hidden, as a strange form of access control?