Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!infopiz!lupine!rfg
From: rfg@NCD.COM (Ron Guilmette)
Newsgroups: comp.lang.c++
Subject: Re: Why just public, protected, and private?
Keywords: protection categories, modularity
Message-ID: <3811@lupine.NCD.COM>
Date: 9 Feb 91 19:26:45 GMT
References: <1991Feb9.021746.13835@xanadu.com>
Organization: Network Computing Devices, Inc., Mt. View, CA
Lines: 18

In article <1991Feb9.021746.13835@xanadu.com> ravi@xanadu.com (Ravi Pandya) writes:
>For some strange reason, C++ allows private messages to be sent either
>to this or to another compatible object, but protected messages can
>only be sent to this.


I don't have my copy of E&S handy, but I believe that your statement is
incorrect.

As I recall, there are at least as many restrictions on calls to private
member functions as there are on calls to protected member function (if
not more).

-- 

// Ron Guilmette  -  C++ Entomologist
// Internet: rfg@ncd.com      uucp: ...uunet!lupine!rfg
// Motto:  If it sticks, force it.  If it breaks, it needed replacing anyway.