Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!shelby!labrea!daemon
From: combs@sumex-aim.stanford.edu (Dave Combs)
Newsgroups: comp.sys.next
Subject: Objective C compiler options
Message-ID: <24042@labrea.Stanford.EDU>
Date: 29 Aug 89 16:51:19 GMT
Sender: daemon@labrea.Stanford.EDU
Lines: 29

Gang,
In the StepStone manuals, there is a section showing and describing the
C code that is generated by the Objective-C part of the compiler (i.e.,
method names are reduced to functions, messages are replaced by calls to
_msg, etc).  One is supposed to be able to get this by giving the -C
option to the compiler.  However, the NeXT version of the GNU compiler
uses the -C option for something completely different (of course! :-( )
Does anyone know of any way that I can get access to this "intermediate"
C code, for tracking down a very strange bug?

Perhaps I can get help on the problem behind all this.  I have a subclass
of Object that contains a TextFieldCell * as an instance variable named
"cell".  The new method for this class (Item) contains the statement
  cell = [TextFieldCell newTextCell:""];

On the first invocation of this Item "new" method, everything is fine.
On the second, the "self" variable for the new Item is somehow
used by TextFieldCell, because after the above statement, even though
self has not changed, [self name] reports "TextFieldCell" as the class,
and the data (dumped in gdb) is all set to look like a TextFieldCell.

Help!!!

Dave  (combs@sumex-aim.stanford.edu)

P.S.  Of course, this all used to work fine all the time.  I'm not sure
if I've uncovered 1)a strange preprocessor bug, 2)a bug in TextFieldCell,
3)a bug in my code, or 4)a bug that's already known about.
Any assistance is GREATLY appreciated.