Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!jpd00964
From: jpd00964@uxa.cso.uiuc.edu
Newsgroups: comp.sys.next
Subject: Re: Help choosing OO C
Message-ID: <246300059@uxa.cso.uiuc.edu>
Date: 12 Oct 89 15:13:00 GMT
References: <72713@linus.UUCP>
Lines: 31
Nf-ID: #R:linus.UUCP:72713:uxa.cso.uiuc.edu:246300059:000:1364
Nf-From: uxa.cso.uiuc.edu!jpd00964    Oct 12 10:13:00 1989


/* Written  8:53 pm  Oct 10, 1989 by fischer@iesd.auc.dk in uxa.cso.uiuc.edu:comp.sys.next */
In article <20717@gryphon.COM> sarima@gryphon.COM (Stan Friesen) writes:
>>It is not clear to us whether we should be using Objective-C or GNU
>>g++.  Can someone give a quick summary of the various features of
>>each, and any advantages/disadvantages of choosing one over the other?
>>
>	Niether, use a real C++ compiler, perhaps even get the ATT
>cfront source code.

And GNU C++ is just about the only C++ *compiler* available for UNIX
pmachines. Remeber, AT&T cfront is a C++- -> C translator, which makes
debugging quite a bit more complicated, and makes compiling take far
more time.

>And if you intend to ever sell your application
>you really do not want to deal with the confusing g++ copyleft stuff.

Now that the FSF (the GNU people) have removed the copyright notices
from the runtime libraries, this should prove much less of a problem.
You can't use the GNU C++ Library (libg++) in commercial applications,
but the compiler should be OK.

/Lars
--
Copyright 1989 Lars Fischer; you can redistribute only if your recipients can.
Lars Fischer,  fischer@iesd.auc.dk, {...}!mcvax!iesd!fischer
Department of Computer Science, University of Aalborg, DENMARK.

"That makes 100 errors; please try again" --TeX
/* End of text from uxa.cso.uiuc.edu:comp.sys.next */