NetNews Usenet Archive 1992 #26/NN_1992_26.iso/spool/comp/sys/next/misc/21974

Text File | 1992-11-14 | 1.9 KB | 42 lines

Newsgroups: comp.sys.next.misc
Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!ns1.nodak.edu!usenet
From: [e-mail] (Todd Enders)
Subject: Re: Why, Why, WHYYYY?? USE OBJECTIVE-C for IB??
Sender: [e-mail] (News login)
Message-ID: <[e-mail]>
Date: Sat, 14 Nov 1992 02:32:01 GMT
Reply-To: [e-mail]
References: <[e-mail]>
Nntp-Posting-Host: bolshoi.cc.misu.nodak.edu
Organization: North Dakota Higher Education Computing Network
Lines: 28

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++?
)
     Really, the amount of Objective-C one needs to learn to handle the
interface created by the IB is pretty minimal.  A couple of days of work is
about all it takes.  Most things are pretty intuitive, but there are some
pitfalls, like anything else.

     My own personal experience?  I knew neither Obj-C or C++, but I managed
to hook an app to it's interface with minimal hair pulling.  The app itself
is strictly ANSI C, with just enough Obj-C to handle the interface issues.
This was *not* a "hello world" class app, BTW.  Are the Obj-C routines optimal?
Probably not.  Does it work?  You bet!  My suggestion?  Spend the time to learn
the necessary bits, then get your app out the door! :-)

Todd     [e-mail]
         uunet!bolshoi!enders
         [e-mail]

>
> Rich