home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.misc
- Path: sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!ira.uka.de!math.fu-berlin.de!news.belwue.de!news.uni-tuebingen.de!andreas
- From: andreas@atlas.physchem.chemie.uni-tuebingen.de (Andreas Haug)
- Subject: Re: GNUPLOT under 3.0
- Message-ID: <andreas.724451478@atlas>
- Sender: news@softserv.zdv.uni-tuebingen.de (News Operator)
- Organization: Comp. Center (ZDV) U of Tuebingen, FRG
- References: <14DEC199219205967@pierre.mit.edu>
- Date: Tue, 15 Dec 1992 20:31:18 GMT
- Lines: 34
-
- chuck@pierre.mit.edu (Chuck Parsons) writes:
- > Has anyone gotton GNUPLOT to compile under 3.0? I'm having
- >trouble in the term module. Specifically, some of the NeXTStep
- >headers (in appkit) with constructs like
-
- > somtheing = (id<NXDraggingInfo>) something else
-
- >refuse to compile. The compiler complains about not being able
- >to find the ")" after the (id. Random attemps to trivially change the
- >syntax (in hopes that it is only a parser bug), like adding spaces
- >do not work. I suspect some knowledge of object oriented c programming
- ----------------------------------------------------------
- >might help.
- ------------
-
- You have given the answer already. The problem is that the objective-C
- code is included from a "plain C" program who's filename ends with ".c".
- Since NextStep 3.0 (really: since GNU-C 1.whatever) the compiler just
- forgets all he knows about objective-c _if_ the source file has the
- ".c"-Extension. So to provide the compiler with knowledge of object
- oriented c programming" one has to use the correct extension.
-
- Workaround: rename "term.c" (if mind serves...) to "term.m", edit the
- Makefile accordingly. (Thanks to Frank Siegert who found this out.)
-
- Best regards,
-
- Andreas.
-
-
- --
- ------------------------------ahaug@mailserv.zdv.uni-tuebingen.de
- "It's not too late to start again; days go by and seasons change;
- nothing stays the same; life's an endless game; between strangers."
-