Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!pfkeb From: pfkeb@ebnextk.SLAC.Stanford.EDU (Paul Kunz) Newsgroups: comp.lang.objective-c Subject: Re: Objective C vs C++ Message-ID: Date: 23 Feb 91 06:06:25 GMT References: <60377@eerie.acsu.Buffalo.EDU> <1991Feb22.092204.24156@ap542.uucp> Sender: news@unixhub.SLAC.Stanford.EDU Organization: Stanford Linear Accelerator Center Lines: 20 Nntp-Posting-Host: ebnextk.slac.stanford.edu In-reply-to: tomnews%apgraph@ap542.UUCP's message of 22 Feb 91 09:22:04 GMT The owners of NeXT machines don't have any choice if programming for the Graphical User Interface kit of objects. It is Objective-C, period. However, for Classes that don't need the GUI, we also have C++ on every machine that has the compiler. In fact, we have Objective-C++ in that our code that seems to be Objective-C can message C++ classes. That is, from Objective-C code we can issue function calls to C++ classes, thus I call the new NeXT compiler an Objective-C++ compiler. Brad Cox, of Objective-C fame, visited me about a year ago. At the lunch we had together, we talked about the differences between C++ and Objective-C. After lunch, I concluded and said to Brad that what the world needed is Objective-C++. Today we have it. Since the NeXT compiler is based on GNU software, NeXT must submit its modifications to GNU. The next release of gcc, as I understand it, will contain NeXT's modifications to make it an Objective-C compiler. I can only assume that the release after that will make gcc a Objective-C++ compiler.