Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!agate!bionet!apple!bloom-beacon!bu-cs!purdue!decwrl!labrea!polya!shap
From: shap@polya.Stanford.EDU (Jonathan S. Shapiro)
Newsgroups: comp.sys.next
Subject: Re: GNU C versus Objective-C
Message-ID: <4608@polya.Stanford.EDU>
Date: 21 Oct 88 18:58:22 GMT
References: <17780@glacier.STANFORD.EDU> <[9.5]karl@ddsw1.alt.next> <12935@oberon.USC.EDU> <5716@hoptoad.uucp>
Reply-To: shap@polya.Stanford.EDU (Jonathan S. Shapiro)
Organization: Stanford University
Lines: 16

In article <5716@hoptoad.uucp> gnu@hoptoad.uucp (John Gilmore) writes:
>According to the info given to the press at the introduction, this is false.
>Objective-C is a preprocessor which generates C code.  This is fed to the
>GNU C compiler.  The GNU debugger and Emacs are also supplied.

One of the things that disturbs me about this is the following:  GNU
emacs is a moving target, and by and large the motion is in positive
directions.  Similarly for the compiler, linker, etc. etc. etc.

To what extent has NeXT altered these components in a way that will
preclude my keeping them up to date off of GNU's distributions?  In
particular, I am concerned about the implications for library
compatibility, or more generally, How do I know that when I upgrade my
GNU compiler to 1.N+1 that it will continue to be compatible with the
portion of the NeXT stuff that is proprietary?

Jon