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: Should I use a generic object which all others inherit from
- Message-ID: <1992Nov22.190424.964@mole-end.matawan.nj.us>
- Summary: It's NOT OOP! It IS OOP! IS NOT! IS! IS NOT! IS! IS NOT! ...
- Organization: :
- References: <3762@news.cerf.net> <1992Nov17.190821.18348@informix.com> <1992Nov20.133441.27425@ucc.su.OZ.AU>
- Date: Sun, 22 Nov 1992 19:04:24 GMT
- Lines: 18
-
- In article <1992Nov20.133441.27425@ucc.su.OZ.AU>, maxtal@extro.ucc.su.OZ.AU (John MAX Skaller) writes:
- > In article <1992Nov17.190821.18348@informix.com> cshaver@informix.com (Craig Shaver) writes:
- > >In article <3762@news.cerf.net> hlf@nic.cerf.net (Howard Ferguson) writes:
-
- > >I have to think some of the people involved with C++ have no idea what the
- > >basis of OOP really is. They are simply using C++ as an improved C.
-
- There's lots of discussion on what `OOP' really is. To some, it is the
- style fostered by a particular OOPL. To others, the meaning is not so much
- in the idiomatic style of message interaction but in encapsulating program
- and data in `objects' and programming with them.
-
- A broader view will allow you to see, understand, and learn more.
- --
- (This man's opinions are his own.)
- From mole-end Mark Terribile
-
- mat@mole-end.matawan.nj.us, Somewhere in Matawan, NJ
-