From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,b8b8a54001adc4d2 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!newsread.com!news-xfer.newsread.com!newspeer.monmouth.com!newsswitch.lcs.mit.edu!nntp.TheWorld.com!not-for-mail From: Robert A Duff Newsgroups: comp.lang.ada Subject: Re: Possible Ada deficiency? Date: 11 Jan 2005 16:08:37 -0500 Organization: The World Public Access UNIX, Brookline, MA Message-ID: References: <1104516913.718856.94090@z14g2000cwz.googlegroups.com> <1105290947.422412.195950@c13g2000cwb.googlegroups.com> <1105327217.641306.80180@c13g2000cwb.googlegroups.com> <1105475874.073304.302190@z14g2000cwz.googlegroups.com> NNTP-Posting-Host: shell01-e.theworld.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: pcls4.std.com 1105477717 30837 69.38.147.31 (11 Jan 2005 21:08:37 GMT) X-Complaints-To: abuse@TheWorld.com NNTP-Posting-Date: Tue, 11 Jan 2005 21:08:37 +0000 (UTC) User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: g2news1.google.com comp.lang.ada:7654 Date: 2005-01-11T16:08:37-05:00 List-Id: danmcleran@hotmail.com writes: > >I've no idea what you're replying to here, > > What I'm replying to is the argument that additional visibility > restrictions aren't warranted because anyone can change the code to > change the visibility. That seems like a pretty silly argument. If one > takes this to the logical extreme, what's the point of having any > information hiding capabilities at all? Couldn't someone always just > change the code and change the visibility? Of course they could. OK, I agree with that. I certainly don't advocate eliminating the visibility rules. > >but note that the point of > >the visibility rules is documentation > > I don't buy this at all. I don't believe that the sole reason for > visibility rules is documentation. There's obviously an intent to > provide some information hiding and separation of interface from > implementation. I agree, but I call that documentation. All this good info hiding and whatnot doesn't affect the input/output behavior of the program. But it does document the logical structure of the program (such as which parts of the code can meddle with which variables). And (as you pointed out in another note), the advantage of *this* kind of documentation (over comments) is that it is trustworthy, whereas comments can and often do contain misinformation. - Bob