public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: bcr@lizardtech.com
To: gnats-gnats@sourceware.cygnus.com
Subject: gnats/217: Information on http://gcc.gnu.org/bugs.html incaccurate
Date: Fri, 13 Jul 2001 10:24:00 -0000	[thread overview]
Message-ID: <20010713172014.9106.qmail@sourceware.cygnus.com> (raw)

>Number:         217
>Category:       gnats
>Synopsis:       Information on http://gcc.gnu.org/bugs.html incaccurate
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 13 10:24:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dr Bill C Riemers
>Release:        gcc 3.0
>Organization:
>Environment:
Web browser
>Description:
On http://gcc.gnu.org/bugs.html , the following text is included:

>       G++ now implements type access control on member types. Defect report 45 
> clarifies that nested classes are members of the class they are nested in, and 
> so are granted access to private members of that class.

There are several problems with this text.  First off, defect 45, talks
about template implimentations, not Nested classes.  So the refered defect
# must be wrong.

Second, according to "C++ Programming Language, Third Edition", by
Bjarne Stroustrup, the creator of C++:

  Section C.11.3.

  The members of a member class have no special access to members
  of an enclosing class.  Simularly members of an enclosing class
  have no special access to members of a nested class; the
  usual access rules (section 10.2.2) shall be obeyed.  For example:

   class Outer {
     typedef int T;
     int i;
   public:
     int i2;
     static int x;
     class Inner {
       int x;
       T y; // error: Outer::T is private
     public:
       void f(Outer *p,int v);
     };
     int g(Inner *p);
  };

...
>How-To-Repeat:

>Fix:
Update the webpage, and confirm the g++ compiler conforms
to this standard.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2001-07-13 10:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010713172014.9106.qmail@sourceware.cygnus.com \
    --to=bcr@lizardtech.com \
    --cc=gnats-gnats@sourceware.cygnus.com \
    /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).