public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "austern at apple dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/17470] Visibility attribute ignored for explicit template instantiation
Date: Tue, 14 Sep 2004 02:20:00 -0000	[thread overview]
Message-ID: <20040914022004.18880.qmail@sourceware.org> (raw)
In-Reply-To: <20040913213750.17470.austern@apple.com>


------- Additional Comments From austern at apple dot com  2004-09-14 02:20 -------
Tastes differ, I suppose!  My own feeling is that it's unnatural, when declaring an unbounded set of 
functions, to have to say that either all of them or none of them get exported.  I find it more likely that 
a dynamic library author would decide that a selected few specializations are the library's interface.

However, I don't insist on that point.  What I do insist on: it's wrong for the compiler to silently ignore 
the visibility attribute on explicit instantiations.  Either it should be honored, or else it should be 
documented and diagnosed as an error.  Silently ignoring it is a nasty trap for users.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17470


  parent reply	other threads:[~2004-09-14  2:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 21:37 [Bug c++/17470] New: " austern at apple dot com
2004-09-13 23:40 ` [Bug c++/17470] " bangerth at dealii dot org
2004-09-14  2:20 ` austern at apple dot com [this message]
2004-09-14  3:48 ` bangerth at dealii dot org
2004-12-13 20:47 ` efrias at syncad dot com
2004-12-22 20:54 ` nomis80 at nomis80 dot org
2004-12-22 20:57 ` nomis80 at nomis80 dot org
2004-12-28 23:53 ` pinskia at gcc dot gnu dot org
2005-09-02  0:17 ` jmegq at radiance dot com
     [not found] <bug-17470-3310@http.gcc.gnu.org/bugzilla/>
2006-03-21  3:29 ` jason at gcc dot gnu dot org
2006-06-23  1:11 ` jason at gcc dot gnu dot org
2006-06-30  2:29 ` jason at gcc dot gnu dot org
2006-06-30 15:30 ` pinskia at gcc dot gnu dot org
2006-08-28 12:29 ` jakub 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=20040914022004.18880.qmail@sourceware.org \
    --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: link
Be 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).