Xref: utzoo comp.object:134 comp.sys.next:3500 comp.lang.c++:5001 gnu.g++:432 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!ctrsol!uakari.primate.wisc.edu!ginosko!uunet!mcsun!sunic!dkuug!iesd!iesd!fischer From: fischer@iesd.auc.dk (Lars P. Fischer) Newsgroups: comp.object,comp.sys.next,comp.lang.c++,gnu.g++ Subject: Re: Help choosing OO C Message-ID: Date: 11 Oct 89 01:53:21 GMT References: <72713@linus.UUCP> <20717@gryphon.COM> Organization: Mathematics and Computer Science, University of Aalborg Lines: 28 In-reply-to: sarima@gryphon.COM's message of 8 Oct 89 16:02:44 GMT 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