Re: How different is obj c from c++?
Peter Remmers <p.remmers@expires-2011-04-30.arcornews.de> wrote:
Am 23.02.2012 12:21, schrieb Juha Nieminen:
Where Objective-C sucks:
- No RAII. Enough said.
(On the Mac OS X platform you can use a limited form of garbage collection
that takes care of eventually freeing objects. However, this feature is not
available on all platforms, eg. on the iPhone. Regardless, RAII is useful
for more than just memory management.)
With Objective-C++ you can have the best of both worlds (to some extent).
To some extent, yes. When I develop for the iPhone I always use
Objective-C++ and have my own smart pointer to handle the reference
counting of Objective-C objects automatically and use it whenever it's
possible and feasible. (Thankfully Apple extended Objective-C++ so that
Objective-C classes can have C++ objects as members, as long as they have
a default constructor. This makes life a lot easier in many cases.)
However, there are many situations where a C++ smart pointer cannot
be used. One example is when using Interface Builder to create your UI.
It doesn't understand Objective-C++, so you have to use Objective-C
properties instead (which in turn need synthesizers and manual releases
in a manually-written deallocator; you can minimize the tediousness and
verbosity of this by using some cleverly made preprocessor macros, but
only to a limited extent).