Path: utzoo!mnetor!tmsoft!becker!hybrid!scifi!bywater!uunet!kgw2!dennisg
From: dennisg@kgw2.bwi.WEC.COM (Dennis Glatting)
Newsgroups: comp.sys.next
Subject: Re: NeXT C++ under 2.0
Message-ID: <1891@kgw2.bwi.WEC.COM>
Date: 18 Jan 91 12:53:03 GMT
References: <1991Jan17.033931.4553@julius.cs.uiuc.edu> <1890@kgw2.bwi.WEC.COM>
Sender: dennisg@kgw2.bwi.WEC.COM
Reply-To: dennisg@Xetron.COM
Distribution: comp
Organization: Xetron Corporation, Cincinnati Ohio
Lines: 21


In article <1890@kgw2.bwi.WEC.COM>, dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) writes:
|> 
|> In article <1991Jan17.033931.4553@julius.cs.uiuc.edu>, march@cs.uiuc.edu (Steve March) writes:
|> |> I'm assuming that due to differences between Objective-C and C++ (such
|> |> as type-safe linkage, method invocation, etc) that there currently 
|> |> exists no way of manipulating AppKit, etc. objects via C++.  
|> 
|> i am   rewritting a task that is (now) based upon c++ and uses
|> my project's core set of Objective-C objects.  we're currently having a
|> problem with ld (/lib/collect crashes with a signal 11) but everything
|> compiles and the assembly code (gad) looks right.
|> 

Objective-C/C/C++ mix/mash works great.  the ld problem is well documented
and there is a (trivial) work around.

--
 ..!uunet!kgw2!dennisg  | Dennis P. Glatting
 dennisg@Xetron.COM     | X2NeXT developer
                        | And now a C++ wienie