public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eisenstatdavid+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/45011]  New: template function specialization: does not respect access specifier
Date: Tue, 20 Jul 2010 21:51:00 -0000	[thread overview]
Message-ID: <bug-45011-19465@http.gcc.gnu.org/bugzilla/> (raw)

$ /ltmp/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/ltmp/bin/g++
COLLECT_LTO_WRAPPER=/ltmp/libexec/gcc/i686-pc-linux-gnu/4.6.0/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: ./configure --prefix=/ltmp --with-gimp=/ltmp --with-mpfr=/ltmp
--with-mpc=/ltmp
Thread model: posix
gcc version 4.6.0 20100720 (experimental) (GCC) 
$ /ltmp/bin/g++ -save-temps test.cc
$ cat test.ii
# 1 "test.cc"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "test.cc"
class C {
 private:
  typedef int Private;
};

template<typename T> void function(typename T::Private);


template<> void function<C>(int parameter) {
}

int main() {
  function<C>(0);
}
$


-- 
           Summary: template function specialization: does not respect
                    access specifier
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: eisenstatdavid+gcc at gmail dot com


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


             reply	other threads:[~2010-07-20 21:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 21:51 eisenstatdavid+gcc at gmail dot com [this message]
2010-07-20 21:54 ` [Bug c++/45011] " pinskia at gcc dot gnu dot org
2010-07-24 20:21 ` pinskia 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=bug-45011-19465@http.gcc.gnu.org/bugzilla/ \
    --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).