🚀 go-pugleaf

In article <1992Sep01.163152.118004@zeus.calpoly.edu> Alex Raftis writes:
> From a previous (long) discussion on this topic, yes, gcc can and will work
> on a NeXT. You have to, however, make some slight modifications to the code
> to get it too work. GNU uses a slightly different naming methods on method
> calls, so you need to patch the code to use NeXT's method. Also, the don't,
> by default, support #import, so you have to turn this feature on. With these
> two items enabled, people reported that the Objective-C compiler worked quite
> well on a NeXT.

So that's the problem that I was having with g++ all afternoon. I just
moved all my c++ source off a Convex to my NeXT to continue development.
I spend the last 3 hours trying to figure out the deal the NeXT gdb. It
kept complaining about "invalid symtab info for method at symbol number
52". I guess it pays to take a usenet break. :=)

> You should be able to get a copy of the discussion from archive sites. I 
> remember one post included patches to make it work.

I just check my favourite archive and they only have the FAQs. Anyone know
where I can find this patch for g++.

Thanks for the unsolicated tip. :=)

Just out of curiosity, I prefer to use the gnu compiler but can anyone give
a good comparision between cc++ and g++ as far as speed, code generation,
etc. And why isn't there a %&*^% man page for cc++.

--
Paul Poh                        Unix Systems Programmer
ppoh@amethyst.tcs.tufts.edu     Computer Services, Tufts University