views:

335

answers:

4

I've been learning C++ for some months now and find it an excellent language albeit its perks.

I was wondering what exactly is the so-called Objective-C++ and if it's worth learning it as a main development language to target Apple environments (ie. Mac OS X, iPhone OS). Searching around the web I only found a couple of good articles: mainly Wikipedia's entry and one from Mac Dev Center.

Wikipedia says:

Objective-C++ is a front-end to the GNU Compiler Collection which can compile source files which use a combination of C++ and Objective-C syntax. Objective-C++ adds to C++ the extensions Objective-C adds to C.

The Mac Dev Center article adds:

Apple’s Objective-C compiler allows you to freely mix C++ and Objective-C code in the same source file. This Objective-C/C++ language hybrid is called Objective-C++. With it you can make use of existing C++ libraries from your Objective-C applications.

The Apple article calls Objective-C++ a language. Is this right?

I would like to know the following:

  • Is it possible to learn and use Objective-C++ without knowing C/Objective-C?
  • Are there any good books, sites, forums, etc where one can get more information and/or help?
  • Are there any big projects done in Objective-C++ as far as you know of?
+7  A: 

Objective-C++ is really just mixing Objective-C with C++. Since it allows syntax from both you could argue that it is a new language.

I primarily use ObjC++ (.mm source files) when I have to interface Objective-C code with some C++ library. It is convenient to be able to call C++ in that case. Personally I do not know a lot of people who actually really mix C++ and Objective-C.

St3fan
A: 

1) i doubt it, because everyone of them is a superset of the C language. i don't consider objective-c++ a totally new language. it is just a mix of both that gives you some additional possibilities - i.e. reuse existing c++ code, or use faster c++ in more time critical code sections, or use c++ code where no objective-c / cocoa interface is exposed (mainly hardware related lowlevel stuff like serial ports / ioctls, opengl, ...)

2) i think resources regarding this topics a

3) pass ... i mean what do you consider big. i just know from a bunch of projects (maybe not all of them commercial in the sense that you can buy the software in the store) that use this mix for the reasons listed in 1.

didito
Actually, C++ is not a superset of the C language. It is very close, but for example C++ is much stricter regarding type conversions, so code that is perfectly valid C might not compile with a C++ compiler. In most cases the differences are actually improvements, IMO, and easily fixed, but I just thought I'd correct this.Funnily, Objective-C is a strict superset of C. Any valid C code is also valid ObjC code.
uliwitness
thanks for pointing that out. i didn't know that.
didito
A: 

Plenty of large projects use some Objective-C++. Camino, Chromium, and Firefox, for example, are all substantial open-source projects that include Objective-C++.

smorgan
+2  A: 

Yes you should learn Objective-C++ when you want to develop competitive comnerical strength (aka so good that people are willing to pay for them) Apple applications.

It is indeed nothing else the Objective-C and C++ combined in the same file.

For Objective-C use any of the hunderts of the popular apple development blogs/mailing lists/newsgroups. Especially the one directly provided by Apple.

For C++ this is the same, dozens of blogs/mailing lists/starter tutorials are there. But while C and its Objective-C add-on is pretty simple and easy to learn if you already understand programming. C++ is a total different and complex beast. Get a few good books and learn it (after 10 years you will be able to fully understand the language :-) but you can writing C++ programs with just a fraction of this knowledge.

So and now the magic question why you should use C++ when you could get away with Objective-C. The answer is pretty simple. Beside the obvious mentioned wrapping of existing C++ libraries, Objective-C is slow, first of all - method call. THe usual adivse is to do something serious in your methods to avoid this runtime penality that shows up in this language.

But especially for Containers you should really consider to use C++ templates. A vector is much much faster then an NSArray. If your dataset is large you will feel the difference. Also i find C++ containers easier to use because they avoid the typecasts you have to do with Objective-C.

With slow ARM CPU's on iPad and iPhone this is not premature optimization.

Unfortunately you can't mix C++ and Cocoa classes and therefore C++ should only be used for algorithmic data. For the GUI you have to use Cocoa and Objective-C classes.

Getting the right balance between C++ and Objective-C is some part of the skills you need to develop as a Apple programmer.

Lothar