home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!kaon.SLAC.Stanford.EDU!pfkeb
- From: pfkeb@kaon.SLAC.Stanford.EDU (Paul F. Kunz)
- Subject: Re: Problems using gcc 2.3.3
- In-Reply-To: samurai@cs.mcgill.ca's message of 31 Dec 92 03:02:09 GMT
- Message-ID: <PFKEB.92Dec30221114@kaon.SLAC.Stanford.EDU>
- Lines: 21
- Sender: news@unixhub.SLAC.Stanford.EDU
- Organization: Stanford Linear Accelerator Center
- References: <1htfq5INNhm3@shelley.u.washington.edu> <C03sFL.D0J@cs.mcgill.ca>
- Date: Thu, 31 Dec 1992 06:11:15 GMT
-
- So here we are...
-
- - gcc 2.3.3 doesn't support NeXT's extensions to Objective-C which
- were introduced with NeXTSTEP3.0 So you can't use gcc for any
- compilation requiring the appkit; cuz it will hit things like
- ``@class'' almost immediately.
-
- - NeXT's cc++ doesn't support GNU's extension to the C++ language which
- were introduced with gcc 2.x. So you can't use cc++ for any
- compilation requiring libg++; cuz it will hit things like
- ``#include-next stdlib.h'' almost immediately.
-
- So if I understand things right (please correct me if I'm wrong), we
- are really in bad shape. We can't use both the latest release of
- gcc/libg++ and NeXTSTEP 3.0 in the same application.
-
- Anybody else find this distrubing?
- --
- Paul F. Kunz pfkeb@slac.stanford.edu (NeXT mail ok)
- Stanford Linear Accelerator Center, Stanford University
- Voice: (415) 926-2884 (NeXT) Fax: (415) 926-3587
-