home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: sparky!uunet!mole-end!mat
- From: mat@mole-end.matawan.nj.us
- Subject: Re: Object What is an OODBMS?
- Message-ID: <1992Aug26.010349.3485@mole-end.matawan.nj.us>
- Summary: Quick Trick Brick Stack
- (Or the difference between What Is and What It Is Made Of
- Organization: :
- References: <RCZ5NS@netmbx.netmbx.de> <BEVAN.92Aug12152127@jaguar.cs.man.ac.uk> <JONAS.92Aug22123325@ipcsun5.his.se>
- Date: Wed, 26 Aug 1992 01:03:49 GMT
- Lines: 61
-
- In article <JONAS.92Aug22123325@ipcsun5.his.se>, jonas@ipcsun5.his.se (Jonas Mellin) writes:
- > In article <BEVAN.92Aug12152127@jaguar.cs.man.ac.uk> bevan@cs.man.ac.uk (Stephen J Bevan) writes:
-
- > In article <RCZ5NS@netmbx.netmbx.de> jrobie@netmbx.netmbx.de (Jonathan Robie) writes:
- > ... we frequently want to use code or data that ... exist in another
- > class. ... if we have a ... LinkedList we might ... use this when
- > implementing our stack. ... we might say that a Stack is a LinkedList
- > which also has the push() and pop() functions. We can do this
- > directly using ... inheritence:
-
- > class Stack : public LinkedList
- > ...
-
- > Is this generally considered good use/example of inheritance? I
- > don't think a "Stack is a LinkedList" at all, rather a LinkedList is
- > a possible implementation of a Stack. I'd therefore use ... a
- > template ...
-
- > I too prefer the view of this that Bevan has, but who is to say that
- > Stack cannot be a LinkedList?
-
- This is the difference between modelling the problem and modelling the
- solution. In general, we _do_ need different tools for modelling
-
- A) Real-world entities and processes
- B) Mathematical entities and processes (mathematical entities
- have no lifetime; math can describe time but it itself
- exists out of time)
- C) Algorithmic entities and the various loosely set-theoretic
- notions that undergird many them
-
- And we must be careful not to confuse implementation tricks with the
- modelling of the `world' in question.
-
- First, I'll make a quick trick brick stack.
- Then I'll make a quick trick block stack.
- You can make a quick trick chick stack.
- You can make a quick trick clock stack.
- (_Fox in Socks_, Dr. Seuss)
-
- The tricks are great for getting a fast implementation, but a fast
- implementation isn't necessarily the one you want for the long term.
- They may be good for prototypers, but they may not be so good for the
- `real product'. The real product has to survive many people working on
- it, and that probably means that it has to be written with an eye
- towards communication. (Of course, if you are a prototyper, the
- prototype _is_ your Real Product ...)
-
- ...
- Clocks on fox tick. Clocks on Knox tock.
- Six sick bricks tick. Six sick chicks tock.
- Please sir, I don't like this trick sir.
- My tongue isn't quick or slick sir.
- I get all those ticks and clocks, sir,
- mixed up with the chicks and tocks sir.
- (ibid.)
- --
- (This man's opinions are his own.)
- From mole-end Mark Terribile
-
- mat@mole-end.matawan.nj.us, Somewhere in Matawan, NJ
-