> I'm not real worried about the syntax, I can read that in a book on my own.
> I guess to state my question more clearly, are C style arrays normally used
> in Objective-C?
Yes, there is no difference with C in that respect.
Quote:> If so are there any limitations/bad points to using them?
There are restrictions on return values or arguments of messages.
These are related to how messages are used in Objective-C (they default to
returning objects and to having objects as arguments).
Some restrictions may exist due to the type casting when other types are used
Basically, the "bad point" may consist of using too many typed constructs,
if you have a great deal of Objective-C messages that do not simply return
objects or take objects as arguments, then something's wrong.
The concept of the Objective-C messenger is that it tries to exchange as
much data as possible as "objects", not as typed data with a C type.
So as a question of programming style, one could say that if a program or
some library that uses Objective-C messages tends to heavily use C types, it
may be a good idea to revise that API, to revise that interface, and see whether it could not be better designed to use objects.