Path: utzoo!utgpu!attcan!uunet!munnari!otc!gregw
From: gregw@otc.oz (Greg Wilkins)
Newsgroups: comp.lang.c++
Subject: Re: Objective-C vs C++
Summary: <sunview.h> is not a good portablility guide!
Message-ID: <485@otc.oz>
Date: 3 Nov 88 22:19:58 GMT
References: <8335@nlm-mcs.arpa> <3438@jpl-devvax.JPL.NASA.GOV>
Organization: OTC Development Unit, Australia
Lines: 21

In article <3438@jpl-devvax.JPL.NASA.GOV>, david@beowulf.JPL.NASA.GOV (David Smyth) writes:

> Face it: the only reason we are talking about using C++ or Objective-C
> is because of a desire to be "upwardly compatible" with existing C
> code.  Note, however, that C++ IS NOT "upwardly compatible" with C,
> rather C++ IS A DIFFERENT LANGUAGE!  Just try including <sunview.h>,
> and you will see what I mean.  Or any large C language program!  

Just try includeing <sunview.h> on any other C compiler, apart from
the difference in function prototyping, there are many other objectionable
things in <sunview.h> that many c compilers would baulk at!. Its full of
comments like {we really must fix this sometime}.

Code wise C++ is upwardly compatible with C. But if you want type checking
between modules, then you have to add the function prototypes.  You can't
get something for Nothing!!.

Greg Wilkins     ACSnet: gregw@otc.oz    UUCP:  {uunet,mcvax}!otc.oz!gregw
|||| OTC ||      Phone:  (02) 287 4862   O/S:   +612 287 2862
				 Fax:    (02) 287 4990   Telex: OTCAA120591
                 Snail:  GPO Box 7000,   Sydney 2001, Australia