2

I would like to learn Objective C, proficiently.

I have a decade of extensive experience and expertise in C# and almost all of the .NET framework. I am also a little familiar with low level concepts. I know what a pointer is.

If I were to start learning Objective C, what are the key things to know before I even start researching the language? For example, do I need to change the way I think about programming, do I need to approach the platform and language in a substantially different way.

Thanks all,

Nick

Nicholas Hill
  • 306
  • 2
  • 18
  • 1
    As you already have knowledge on OOP, you might want to check this q: http://stackoverflow.com/questions/5677655/what-are-the-key-concepts-for-an-iphone-developer-to-learn – ludesign Nov 02 '11 at 10:26

2 Answers2

5

Apple Developer site is one of the most important and useful for learning. Register on it and get access to many articles and docs:

And example: Learning Objective-C: A Primer

beryllium
  • 29,669
  • 15
  • 106
  • 125
3

do I need to change the way I think about programming, do I need to approach the platform and language in a substantially different way.

Not substantially different, but different. The key thing to remember with Objective-C is that its model is much more in the spirit of Smalltalk's message passing paradigm than any of the C++-alike languages like Java and C#. You do not call methods of an object, you send messages to an object and it is the object that decides what code to run at run time. So you can actually send any message to any object (although the object might choose to throw an unrecognised selector exception) and you can change the behaviour of objects at run time.

Also, inheritance is used much less in Objective-C than other OO languages and you'll need to get very familiar with the delegate pattern (not to be confused with C# delegates).

You'll be surprised at the range of different collection classes i.e. it's very small. There's an array, a dictionary (map) and a set and mutable versions of each plus a few other relatively uncommon variants of these. There aren't a bazillion versions of each collection, one for each possible underlying implementation as in Java. The philosophy is "here's an API, let the runtime designers worry about the implementation".

Oh, and try to avoid using exceptions.

JeremyP
  • 84,577
  • 15
  • 123
  • 161