Re: ObjC 3D engine
Re: ObjC 3D engine
- Subject: Re: ObjC 3D engine
- From: Jonathan deWerd <email@hidden>
- Date: Sat, 23 Jun 2007 23:09:00 -0600
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? Originally I wanted to keep plain ObjC, but
there were some really cool labor saving features in C++ that I
finally broke down and used (templates for vector and matrix types.)
Don't worry, the C++ vector and matrix classes automatically convert
themselves to their O3Value counterparts (like toll free bridging for
lamers). But I really wanted speed, especially in the math part, even
though in hindsight I probably didn't need it. True toll free
bridging would have required all type info to be kept in memory at
runtime even if it wasn't needed, and with cache being so precious
nowdays...
I really need to stop myself from premature optimization. Maybe
working on a team would help :)
This would be an absolute godsend to me. I was just today lamenting
the fast that the rich Cocoa library doesn't do much 3D and how the
lack of such a framework was hindering me. Sadly, I couldn't offer
any help, just thank you immensely if you were to ever make your work
available.
Glad to hear it!
Well, not glad that you have a problem, but I am glad that perhaps
all my time wasn't wasted :)
Attachment:
PGP.sig
Description: This is a digitally signed message part
_______________________________________________
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