home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!paladin.american.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!news
- From: brown@ccit02.duq.edu (Jason Brown)
- Subject: Re: Replacing NeXT cc with gcc-2.2.2
- Organization: Columbia University Center for Telecommunications Research
- References: <1992Aug31.164909.7198@fcom.cc.utah.edu>
- Message-ID: <1992Aug31.174501.10595@ctr.columbia.edu>
- Sender: news@ctr.columbia.edu (The Daily Lose)
- Date: Mon, 31 Aug 1992 17:45:01 GMT
- X-Posted-From: ccit02.duq.edu
- X-Posted-Through: sol.ctr.columbia.edu
- Lines: 32
-
- In article <1992Aug31.164909.7198@fcom.cc.utah.edu>
- swillden@news.ccutah.edu (Shawn Willden) writes:
- > Note to readers of comp.lang.c++: I am cross-posting this because
- questions
- > 2, 3, and 4 are applicable and I want opinions/facts from all you C++
- gurus.
- >
- > Hi, I have a few questions about replacing cc with gcc (I have NeXTStep
- 2.0, BTW)
- >
- > 1) I understand that the newest version of gcc incorporates NeXT's
- > Objective-C extensions. Is gcc lacking anything? Is NeXT making any
- new
- > additions to their compiler for 3.0 that may not be present in the
- current
- > version of gcc?
- >
-
- The only thing that I am aware of in the 3.0 NeXT verison of the Compiler
- is support for pre-compiled headers. Makes compiling go quick like a
- bunny. Now you can just #import <appkit/appkit.h> and quit worrying
- about which headers have which prototypes.
-
- --Jason Brown
- brown@ccit01.duq.edu
- ____ __
- / / )
- / _, , __ /-,' ,_ __
- \_/__</_/>_(_/_/\/ /__)__/__(_/__(_/_)_/\/
-
- "Remember, be humble, always answer the phone...
- No matter who's in the car." Jack Lemmon
-