Re: ObjC 3D engine
Re: ObjC 3D engine
- Subject: Re: ObjC 3D engine
- From: Kaelin Colclasure <email@hidden>
- Date: Mon, 25 Jun 2007 09:59:38 -0700
On Jun 23, 2007, at 10:09 PM, Jonathan deWerd wrote:
Actually, there is one more design decision I would like everyone's
input on: should I (we, hopefully) stick with the ObjC++ interface
I have currently (mostly C++ for the math stuff), or should we go
with a more CF like design?
My 2 cents:
First, make sure you are taking every possible advantage of things
like veclib <http://developer.apple.com/hardwaredrivers/ve/
vector_libraries.html> which Apple constantly polishes to get the
most out of all available hardware.
Second, if you *must* use C++ keep it isolated into dedicated (and
hopefully small), performance-critical modules -- ideally that are
compiled as a separate target from the bulk of your project. I
recommend against falling into the practice of using ObjC++ for all
of your sources. Your compilation times suffer, and more insidiously
the incompatibility between ObjC and C++ exceptions makes it
extremely tricky to use either safely.
-- Kaelin
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden