home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cimshop!davidm
- From: davidm@consilium.com (David S. Masterson)
- Newsgroups: comp.databases.theory
- Subject: Re: Data abstraction v/s information hiding
- Message-ID: <DAVIDM.93Jan6115747@consilium.com>
- Date: 6 Jan 93 19:57:47 GMT
- References: <1992Dec22.182220.26096@cs.brown.edu>
- Sender: root@cimshop.UUCP
- Distribution: comp
- Organization: Consilium Inc., Mountain View, California
- Lines: 26
- In-reply-to: yab@cs.brown.edu's message of 22 Dec 92 18:22:20 GMT
- X-Posting-Software: GNUS 3.13 [ NNTP-based News Reader for GNU Emacs ]
-
- >>>>> On 22 Dec 92 18:22:20 GMT, yab@cs.brown.edu (Yashesh Bhatia) said:
-
- > Data Abstraction & information hiding
-
- > Data abstraction, I feel is the hiding of the low level implentation of the
- > data structure from the operations that are performed on it.
-
- > I am not really sure as to what information hiding is, seems to be similar.
-
- Your definition for data abstraction is actually much better as a definition
- for information hiding. Data abstraction is more of a process of finding
- similarities in the definition of two separate data items and reorganizing the
- items so that both could take advantage of the same definition for those
- similarities (ie. instead of two similar definitions, there would be only one
- defintion). People might claim that you can do data abstraction when you only
- have one item, but this is only preparing the one item for another TBD item
- that will take advantage of the abstraction.
- --
- ====================================================================
- David Masterson Consilium, Inc.
- (415) 691-6311 640 Clyde Ct.
- davidm@consilium.com Mtn. View, CA 94043
- ====================================================================
- "The real test of an artist, of course, is not whether you can see each blade
- of grass, but whether the eyes follow you across the room."
- -- Stewart Evans
-