Xref: utzoo comp.lang.eiffel:1356 comp.object:2480
Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!ames!pasteur!galileo.berkeley.edu!jbuck
From: jbuck@galileo.berkeley.edu (Joe Buck)
Newsgroups: comp.lang.eiffel,comp.object
Subject: Re: Inheritance and Information Hiding
Message-ID: <10612@pasteur.Berkeley.EDU>
Date: 30 Jan 91 18:45:13 GMT
References: <1991Jan23.224203.3206@runx.oz.au> <1991Jan24.214652.18515@Think.COM> <808@puck.mrcu>
Sender: news@pasteur.Berkeley.EDU
Reply-To: jbuck@galileo.berkeley.edu (Joe Buck)
Lines: 16

In article <808@puck.mrcu>, paj@mrcu (Paul Johnson) writes:
|> The big advantage of Eiffel over C++ is that thanks to conceptual
|> simplicity, all the dangerous things in Eiffel can be clearly
|> signposted.  C++ forces you to take the blade-guards off in order to
|> use it.  The private/protected/public system is just sugar and I
|> cannot see how it helps anyone.  I can see how it would get in their
|> way though.

Read Grady Booch's book and he'll tell you why.  The private/protected/
public feature is one of his favorite things about the language, and
he gives good arguments.  The problem is that you need to know how to
use it.

--
Joe Buck
jbuck@galileo.berkeley.edu	 {uunet,ucbvax}!galileo.berkeley.edu!jbuck