On Apr 17, 2012, at 9:03 AM, Lee Ann Rucker wrote: > You can keep much of your C++ by using ObjectiveC++.
Yes. You still want to control the boundaries between these two layers of your system and not just make everything Obj-C++ by default. But using C++ from specific Objective-C code is *vastly* easier than constructing an entire layer to provide plain C access to your C++, and then using that from Objective-C. And note that by that comment about controlling boundaries, I'm not advocating necessarily creating specific Objective-C wrappers around the C++ and making that your only Objective-C++. I'm just saying you should know where you use it and why--for instance, in my case, nearly every window controller is Objective-C++, so I do use it widely. But I also have plenty of UI utilities that are pure Objective-C, and the entire "middleware" layer is pure C++, and there's even pure C, as appropriate. -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
