dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) (01/18/91)
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. -- ..!uunet!kgw2!dennisg | Dennis P. Glatting dennisg@Xetron.COM | X2NeXT developer | And now a NeXT/C++ geek
dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) (01/18/91)
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
waltrip@capd.jhuapl.edu (01/18/91)
In article <1891@kgw2.bwi.WEC.COM>, dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) writes: [...material deleted...] > Objective-C/C/C++ mix/mash works great. the ld problem is well documented > and there is a (trivial) work around. > I'd sure be interested in where the ld problem is documented and what workaround is. Bet others would be, too :^) c.f.waltrip DDN: <waltrip@capsrv.jhuapl.edu> Opinions expressed are my own.
dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) (01/19/91)
In article <1991Jan18.105634.1@capd.jhuapl.edu>, waltrip@capd.jhuapl.edu writes: |> In article <1891@kgw2.bwi.WEC.COM>, dennisg@kgw2.bwi.WEC.COM (Dennis Glatting) |> writes: |> [...material deleted...] |> > Objective-C/C/C++ mix/mash works great. the ld problem is well documented |> > and there is a (trivial) work around. |> > |> I'd sure be interested in where the ld problem is documented and what |> workaround is. Bet others would be, too :^) |> the problem isn't /bin/ld, it happens when /bin/ld invokes /lib/collect under csh. somehow the csh stacksize is hardwired. the fix is to put "limit stacksize 10000" in your .cshrc. this will work in _most_ cases. it is claimed that NeXT make has this value hardwired. it will be fixed in a later release. the work around may _not_ work for those of you using NeXT make under 2.0. Since I use GNUmake 3.59 whatever the problem is doesn't exist. -- ..!uunet!kgw2!dennisg | Dennis P. Glatting dennisg@Xetron.COM | X2NeXT developer | And now a NeXT/C++ wienie