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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b5b75c5bf3ae7291 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-08 14:37:32 PST Newsgroups: comp.lang.ada Path: bga.com!news.sprintlink.net!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!lll-winken.llnl.gov!noc.near.net!inmet!panther!brennan From: brennan@panther.warm.inmet.com (William Brennan) Subject: Re: Implement Inheritance (Ada83)? Message-ID: Sender: news@inmet.camb.inmet.com Organization: Intermetrics, Inc. References: <3jiala$kqs@explorer.csc.com> Date: Wed, 8 Mar 1995 21:38:31 GMT Date: 1995-03-08T21:38:31+00:00 List-Id: In article <3jiala$kqs@explorer.csc.com>, Jeff Seigle wrote: >[...] >Years ago I wrote Fortran programs that used a quirk of the >language to implement encapsulation... >The big negative is that once the code is >written there is no enforcement of your wonderful ideas, and the next >one to come along with a mod can stomp down all of your imaginary fences. And even having a design technique supported by the language is not enough. Almost all of the packages I have written over the past 5 years use private types for data abstraction. I have regularly seen occurences where some maintainer would come by, figure he/she didn't have immediate enough access to the type and move it into the visible part of the spec, breaking the encapsulation, of course. One can hear them muttering under their breath: "What's this _private_ stuff for anyway, it's only getting in my way!" Most of the people I work with seem to think that "encapsulation" is a concept developed by academics for hypothetical programs. If they know what it is at all. Yikes! -- ---------------------------------------------------------------------------- === Team-Ada member === Bill Brennan brennan@panther.warm.inmet.com