This is the first in a two-part quiz on the fundamentals of Objective-C. In part 1, you’ll have your knowledge tested with a series of theory-based multiple-choice and true/false questions. In part 2, we’ll move on to pure code. Think you understand the fundamentals of Objective-C? Let’s find out.
Enjoyed this Post?
Subscribe to our RSS Feed, Follow us on Twitter or simply recommend us to friends and colleagues!
Join our newsletter!
Freelance Jobs
Create a Tutorial, Get Paid!
Have something to teach the world? Want to earn money doing it? Tutorials, screencasts, and articles published here on Mobiletuts+ are largely contributed by readers just like you! We'll pay you great money for good content. Find Out More
89% :) Very nice
74.07%
not good, but not bad since I’m not an Objc dev.
by the way, this quiz introduced a bit of foundation framework questions. remember that the alloc method is actually a method defined in NSObject, which is not a part of the core language.
Got 85.19%. Not bad, but could have been better.
USELESS … Using iPad .. No button or link to begin ???
88.9 – am happy (and surprised) I did that well…
Thanks for making quiz avail. It emphasized my weak areas needing improvement. Thanks.
I score a 96.3% (26/27) the only question i did wrong was the one about the “without an gc objects allocated must be released”,
This is true until xcode <4.2 because the beta of 4.2 includes the automatic reference counting feature.
Soon or later an allocated should be released, or this means that the object lives for the whole application.
96.3% but I believe Question 18 is wrong, or at least badly worded. It states “Formal protocols in Objective-C are compiler-enforced”. The tests says this is true, when it in fact isn’t. Formal protocols are compiler checked, but not compiler enforced, as they only result in warnings.
That’s exactly what I was thinking.
Good catch Martin.
Contrary to the test, Objective-C messages are checked by the compiler: in the message call:
[NSString stringWithString:2]; for example, the compiler checks the types of the arguments, and reports a type error.
Now in [foo performSelector:@selector(fum)];, the compiler does not check that foo’s type can actually execute “fum” but that is a different matter. The question as stated is not clear enough to warrant its answer.
Got 84.67 something. Not bad actually but need to improve myself.
Nice questions.
Great job, thanks a lot!!
Sigh….dream to make an iOS app has shuttered….
An orc would have performed just as good as you! You scored 62.96%
cool…more! i got job interviews coming up need the practice
though i only scored 89 so have decided to cover my flat in virtual post it notes with objC rules :)
You’re awesome enough to just walk into Mordor, aren’t you? You scored 100%
:-) Didn’t even expect that after not touching Objective-C for over a year now.
92.59%
Not bad for a couple weeks of learning. But, as for me, questions were very easy, even you’re not experienced developer.
P.S. Hello from Ukraine :)
Any clue when part two is available? I missed three of them, (88.89%) but that is because one was worded funny, and other is debatable as discussed by DavidPhillipOster already. So no Mordor yet.
96.3 %
92,59%, 2 bad answers.
Thanks for the quiz, not taking the 2nd one.