Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!bellcore!faline!ulysses!hector!jss
From: jss@hector.UUCP (Jerry Schwarz)
Newsgroups: comp.lang.misc,comp.lang.smalltalk,comp.lang.c++
Subject: Re: C++ vs Objective-C
Message-ID: <2996@ulysses.homer.nj.att.com>
Date: Tue, 22-Sep-87 11:16:08 EDT
Article-I.D.: ulysses.2996
Posted: Tue Sep 22 11:16:08 1987
Date-Received: Thu, 24-Sep-87 07:18:09 EDT
References: <3405@ece-csc.UUCP> <638@its63b.ed.ac.uk> <1811@watcgl.waterloo.edu> <1971@tekig5.TEK.COM>
Sender: daemon@ulysses.homer.nj.att.com
Reply-To: jss@hector (Jerry Schwarz)
Organization: AT&T Bell Labs, Murray Hill
Lines: 20
Xref: mnetor comp.lang.misc:676 comp.lang.smalltalk:327 comp.lang.c++:444

In article <1971@tekig5.TEK.COM> tomm@tekig5.UUCP (Tom Milligan) writes:
>kdmoen@watcgl.waterloo.edu (Doug Moen) writes:
>
>Both Objective-C and C++ are C language Preprocessors.  Thus the capablility
>exists in both to write "standard" C code.  And both produce as their output,
>"standard" C code.  

I can't say with respect to Objective-C, but with regards to C++ this
is not the case.  C++ is a language that is (mostly but not 100%) an
extension of C.  The commonly available compiler does use C as an
intermediate language, but it is not a preprocessor.   The pragmatic
justification for this assertion is that if the C compiler ever
produces an error message while compiling the intermediate code
produced by the C++ front-end it is a bug or limitation in the C
compiler or the C++ front-end. I can assert this without looking at
the source code being compiled.

Jerry Schwarz
Bell Labs
Murray Hill