www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/09/15/06:37:31

Xref: news2.mv.net comp.os.msdos.djgpp:8632
Newsgroups: comp.os.msdos.djgpp
From: design AT netcom DOT com (Chris Waters)
Subject: Re: protected and public base classes
Message-ID: <designDxroL9.sx@netcom.com>
Organization: Design and Delivery
References: <51frft$9qk AT miracle DOT cybernex DOT net>
Date: Sun, 15 Sep 1996 09:19:57 GMT
Lines: 20
Sender: design AT netcom20 DOT netcom DOT com
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

In article <51frft$9qk AT miracle DOT cybernex DOT net>,  <mrichman AT cybernex DOT net> wrote:

>Is there ever a case in djgpp when access to the members of protected
>base classes is different from the access to members of public base
>classes?  Does djgpp conform to the ansi standard in this regard?

To the best of my knowledge, there is no protected inheritance in C++.
If there were (if there is), then I assume it would work the same as
protected members:  only derived classes would be aware of the
inheritance and able to access the members of the protected base class.
Obviously this would be different.

Since there is, as yet, no ansi standard for C++, the question about
djgpp's conformance is meaningless.  Unless you're asking about
conformance with the C standard.  :)

Questions about the current draft of the standard really belong in
comp.std.c++ (although it might help to read a few posts there, and
check out the faq and web pages first).  Questions about C and C++ as
implemented in gcc should be asked in gnu.gcc or gnu.g++.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019