public inbox for
help / color / mirror / Atom feed
* gnats/217: Information on incaccurate
@ 2001-07-13 10:24 bcr
  0 siblings, 0 replies; only message in thread
From: bcr @ 2001-07-13 10:24 UTC (permalink / raw)
  To: gnats-gnats

>Number:         217
>Category:       gnats
>Synopsis:       Information on 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
>Originator:     Dr Bill C Riemers
>Release:        gcc 3.0
Web browser
On , 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;
     int i2;
     static int x;
     class Inner {
       int x;
       T y; // error: Outer::T is private
       void f(Outer *p,int v);
     int g(Inner *p);


Update the webpage, and confirm the g++ compiler conforms
to this standard.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2001-07-13 10:24 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-13 10:24 gnats/217: Information on incaccurate bcr

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).