I think there are "many" situations where this approach is used/ could be useful, for example, when you have your UI in cocoa and you want to communicate with the C++ objects. Ofcourse you can mix obj-c and c++ in a trivial way but that means your application sees both obj-c and C++ types. A classic example would be an alternative for objective c bindings for CORBA/SOAP. You can have Objective C wrappers over C++ bindings available for SOAP/CORBA and use them in your application without your code been aware of the C++ objects/types. I don't know if I made my point clear :)
On Fri, Apr 3, 2009 at 8:26 AM, Scott Ribe <scott_r...@killerbytes.com>wrote: > I don't see the point. I work extensively with Objective-C++ and I don't > think I've ever seen a single situation where wrapping C++ objects in > Objective-C wrappers would have been a good approach. > > -- > Scott Ribe > scott_r...@killerbytes.com > http://www.killerbytes.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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
