Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!munnari!moncskermit!goanna!yabbie!koel!rcopm
From: rcopm@koel.rmit.oz (Paul Menon)
Newsgroups: comp.lang.c++
Subject: Re: C++ vs Objective-C
Message-ID: <308@koel.rmit.oz>
Date: Thu, 24-Sep-87 21:15:36 EDT
Article-I.D.: koel.308
Posted: Thu Sep 24 21:15:36 1987
Date-Received: Sun, 27-Sep-87 10:20:42 EDT
Organization: RMIT Comm & Elec Eng, Melbourne, Australia.
Lines: 25


  The argument about which is better between C++ and Objective-C so far has
been a matter of how "powerful" each language is.  Since both are "successors"
to C, each inherit the same property of being very writable, but very 
unreadable.  Anything either does to improve the situation, has to be an
advantage.  This is where, in my opinion (and that's all it is) Objective-C
is streets ahead of C++.  C++ further confuses the issue with overloading, etc.
The Object-Oriented features of Objective-C stand out like a sore thumb to any
Smalltalk reader.  The added features of C++ do not.  One can migrate to an
almost non-C like language in Objective-C, which gets rid of it's 
unreadability.  To be productive doesn't mean to write compact code, that's 
what the gurus would have you believe.  It is being able to understand a 
program/package quickly, and use high level, easy to understand tools to 
build on or create.  C++ does not do this.  Objective-C does.

Paul Menon.

    Dept of Communication & Electronic Engineering,
    Royal Melbourne Institute of Technology,
    124 Latrobe St, Melbourne, 3000, Australia
 
ACSnet: rcopm@koel             UUCP: ...!seismo!munnari!koel.rmit.oz!rcopm
CSNET:  rcopm@koel.rmit.oz     ARPA: rcopm%koel.rmit.oz@seismo
BITNET: rcopm%koel.rmit.oz@CSNET-RELAY
PHONE:  +61 3 660 2619.