public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13905] Use of __attribute__ ((visibility("X"))) in class and struct declarations Date: Wed, 28 Jan 2004 23:12:00 -0000 [thread overview] Message-ID: <20040128231243.4633.qmail@sources.redhat.com> (raw) In-Reply-To: <20040128224951.13905.s_gccbugzilla@nedprod.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-28 23:12 ------- We are no going to do it. The point is that it makes things look werid like: class __attribute__((visibility("public"))) T { private: int i; //is this public or private? }; The point I was trying to make is that if you want the default accessor to be public use struct instead of class. Also I forgot to mention we should not always follow M$ and their crappy compilers. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13905
next prev parent reply other threads:[~2004-01-28 23:12 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-28 22:50 [Bug c++/13905] New: " s_gccbugzilla at nedprod dot com 2004-01-28 22:53 ` [Bug c++/13905] " pinskia at gcc dot gnu dot org 2004-01-28 23:07 ` s_gccbugzilla at nedprod dot com 2004-01-28 23:12 ` pinskia at gcc dot gnu dot org [this message] 2004-01-28 23:14 ` s_gccbugzilla at nedprod dot com 2004-01-28 23:16 ` s_gccbugzilla at nedprod dot com 2004-01-28 23:19 ` pinskia at gcc dot gnu dot org 2004-01-28 23:52 ` s_gccbugzilla at nedprod dot com 2004-01-29 3:16 ` giovannibajo at libero dot it 2004-01-29 3:25 ` pinskia at gcc dot gnu dot org 2004-01-29 20:01 ` s_gccbugzilla at nedprod dot com 2004-01-30 2:52 ` giovannibajo at libero dot it 2004-01-30 4:35 ` dannysmith at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040128231243.4633.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).