public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	pcarlini@unitus.it, zach@cs.uni-bonn.de
Subject: Re: c++/8355: befriending a template in another namespace
Date: Wed, 20 Nov 2002 14:47:00 -0000	[thread overview]
Message-ID: <20021114123841.2717.qmail@sources.redhat.com> (raw)

Synopsis: befriending a template in another namespace

State-Changed-From-To: open->analyzed
State-Changed-By: paolo
State-Changed-When: Thu Nov 14 04:38:33 2002
State-Changed-Why:
    Confirmed 3.2.1 pre and 3.3 exp. This is an useful link
    http://www.cuj.com/experts/2101/sutter.htm
    and these two summarizing test cases which do not
    compile and should:
    
    // Example 1 again
    //
    namespace boost {
      template<typename T> void checked_delete( T* x ) {
        // ... other stuff ...
        delete x;
      }
    }
    class Test {
      ~Test() { }
      friend void boost::checked_delete( Test* x ); // the original code
    };
    
    int main() {
      boost::checked_delete( new Test );
    }
    
    ///////////////////////////////
    
    // Example 2: The other way to declare friendship
    //
    namespace boost {
      template<typename T> void checked_delete( T* x ) {
        // ... other stuff ...
        delete x;
      }
    }
    class Test {
      ~Test() { }
      friend void boost::checked_delete<>( Test* x );
    };
    
    int main() {
      boost::checked_delete( new Test );
    }
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8355


             reply	other threads:[~2002-11-14 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 14:47 paolo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-25  8:46 zach

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=20021114123841.2717.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=pcarlini@unitus.it \
    --cc=zach@cs.uni-bonn.de \
    /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).