🚀 go-pugleaf

Richard D Warner writes:
>     I'm a developer who just wants to get a product out the door, and
> I'm frustrated about having to learn a new language just to interface with
> IB.  I know you're supposed to be able to insert ANSI or C++ code into IB
> but I haven't been able to yet.  You still need to know what's going on
> with the implementation files (in Objective-C).  It's supposed to
> be "easier", but easier than what???  Why doesn't NeXT come up with a 
> version of IB written for C++?  

Since you know the story on why Objective-C in the first place (when NeXT was  
selecting only OC had dynamic binding and the C++ vs. OC race was yet to be  
run) the question is really why did NeXT not change over once C++ became the  
widely accepted language it is today and OC never became widely accepted.

First, a rumor floated around that NeXT looked at converting NeXTSTEP from OC  
to C++ and estimated they would have to suspect all software engineering for a  
long time to do the conversion. Second, providing a better C++ interface  
without converting all NeXTSTEP code to C++ makes some sense but I get the  
impression NeXT would just as soon see a third party do that work. Third, NeXT  
has started to take proactive steps to get Objective-C more accepted (e.g.,  
donation/support to FSF, strong consideration on allowing the development tools  
to be ported).

If you have already written lots of C++ that compiles stand-alone (can compile  
on normally configured NeXT development system or with public domain libraries)  
then I strongly suggest that you write a thin layer of Objective-C that fits  
just on top of your C++ codes. The layer becomes the stuff to work with in  
Interface Builder. Oh, and it takes a competent C programmer less than eight  
hours to catch onto Objective-C ... in our experience which I have heard widely  
shared.

Good luck,

Mark R. Thomsen