home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.objective-c
- Path: sparky!uunet!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!homer.cs.mcgill.ca!news
- From: samurai@homer.cs.mcgill.ca (Darcy Brockbank)
- Subject: Re: Objective-C vs. C++
- Message-ID: <1992Aug28.182704.10020@cs.mcgill.ca>
- Sender: news@cs.mcgill.ca (Netnews Administrator)
- Reply-To: samurai@uriel.cs.mgill.ca
- Organization: SOCS, McGill University, Montreal, Canada
- References: <rmartin.714926059@thor>
- Date: Fri, 28 Aug 1992 18:27:04 GMT
- Lines: 25
-
- In article <rmartin.714926059@thor> rmartin@thor.Rational.COM (Bob Martin)
- writes:
- > But, with a few notable exceptions, the industry is putting its muscle
- > behind C++.
-
- Don't forget that C++ came from "The people that brought you UNIX,"
- ATT. Objective C came to you from Stepstone.
-
- I'd bet that ATT had a little more influence than Stepstone in
- the marketplace, and as a result, C++ became "standard" (in quotes
- because the standard C++ isn't quite ready).
-
- > I know why I, and a few of my friends and associates made that choice;
- > but I can't speak for the whole industry. We wanted formality because
- > we were tired of fighting the maintenance nightmares caused by the
- > casual nature of C. We wanted the compiler to lay down strong typing
- > rules, const rules, rules about instantiating abstract classes, rules
- > about downcasting and upcasting. We wanted our programs to be
-
- Isn't ANSI C pretty strong about this? I know gcc2.2.2 drives me
- WILD with warnings :-). And Objective C (well, NeXT's anyway)
- is ANSI.
-
- - db
-
-