public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de> To: gcc-gnats@gcc.gnu.org Subject: c++/7522: access by friend function's default argument Date: Wed, 07 Aug 2002 08:46:00 -0000 [thread overview] Message-ID: <20020807124010.31643.qmail@sources.redhat.com> (raw) >Number: 7522 >Category: c++ >Synopsis: access by friend function's default argument >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Aug 07 05:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Christoph Ludwig <cludwig@cdc.informatik.tu-darmstadt.de> >Release: gcc version 3.1 >Organization: >Environment: Linux 2.4.10-4GB i686 (SuSE 7.3) >Description: g++ 3.1 rejects access to a private class member by the default argument of a friend function. But clause 11, paragraph 7, of the C++ standard seems to allow the access. g++ -v gives the following: Reading specs from /home/lidiaadm/gcc-3.1/gcc-3.1/lib/gcc-lib/i686-pc-linux-gnu/3.1/specs Configured with: ./configure --prefix=/home/lidiaadm/gcc-3.1/gcc-3.1 --enable-threads=posix --enable-languages=c,c++ Thread model: posix gcc version 3.1 gcc 3.0.3 and 2.95.3 (Linux/i) as well as 2.95.2 (Solaris 8 / UltraSparc) show the same behaviour. Regards Christoph Ludwig >How-To-Repeat: g++ -c friend_default.cc >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="friend_default.cc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="friend_default.cc" Y2xhc3MgQSB7CnByaXZhdGU6CiAgICBzdGF0aWMgY29uc3QgaW50IGRhdGE7CiAgICAKICAgIGZy aWVuZCBpbnQgZihpbnQpOwp9OwoKY29uc3QgaW50IEE6OmRhdGEgPSA1OwoKaW50IGYoaW50IGQg PSBBOjpkYXRhKSB7Cn0KCg==
next reply other threads:[~2002-08-07 12:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-07 8:46 Christoph Ludwig [this message] 2002-10-30 15:32 bangerth 2002-10-31 8:46 Christoph Ludwig 2002-10-31 9:24 bangerth 2003-01-17 8:46 Christoph Ludwig 2003-01-28 16:58 bangerth
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=20020807124010.31643.qmail@sources.redhat.com \ --to=cludwig@cdc.informatik.tu-darmstadt.de \ --cc=gcc-gnats@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).