public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/14926] [3.4/3.5 regression] forward declarations and strong using Date: Mon, 12 Apr 2004 20:40:00 -0000 [thread overview] Message-ID: <20040412194827.7234.qmail@sources.redhat.com> (raw) In-Reply-To: <20040412174718.14926.vassili_bourdo@softhome.net> ------- Additional Comments From gdr at integrable-solutions dot net 2004-04-12 19:48 ------- Subject: Re: [3.4/3.5 regression] forward declarations and strong using "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes: | ------- Additional Comments From bangerth at dealii dot org 2004-04-12 19:03 ------- | Alright then. I thought that this is something we should think about | for the C++ side (not the libstdc++ side) regarding the semantics we | give the strong using extension. However, you are right that we do | not have to worry about this: as far as the library is concerned, the | user can't rely on forward declaring stuff anyway (we are, IIRC, allowed | to introduce additional template default parameters for example), and if Err, we're not allowed to introduce additional default template parameters (contrary to what the latitude parameters for non virtual member functions) | this happens in user space with a user using "strong using", we can simply | tell him to forward declare in the right namespace. Yes, "strong using" is for the super user :-) -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14926
next prev parent reply other threads:[~2004-04-12 19:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-12 17:57 [Bug libstdc++/14926] New: libstdc++ rejects forward declarations vassili_bourdo at softhome dot net 2004-04-12 18:03 ` [Bug libstdc++/14926] " vassili_bourdo at softhome dot net 2004-04-12 18:37 ` vassili_bourdo at softhome dot net 2004-04-12 18:42 ` vassili_bourdo at softhome dot net 2004-04-12 18:43 ` [Bug c++/14926] [3.4/3.4 regression] forward declarations and strong using bangerth at dealii dot org 2004-04-12 18:54 ` [Bug c++/14926] [3.4/3.5 " pcarlini at suse dot de 2004-04-12 18:58 ` gdr at integrable-solutions dot net 2004-04-12 19:03 ` gdr at integrable-solutions dot net 2004-04-12 19:03 ` gdr at integrable-solutions dot net 2004-04-12 20:00 ` [Bug libstdc++/14926] " bangerth at dealii dot org 2004-04-12 20:40 ` gdr at integrable-solutions dot net [this message] 2004-04-12 20:41 ` bangerth at dealii dot org 2004-04-12 22:14 ` llewelly 2004-04-12 22:15 ` llewelly at xmission dot com 2004-04-12 22:54 ` bangerth at dealii 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=20040412194827.7234.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).