Question

Actually I am from java background and I am learning objective c.I am very confused about strange behaviour of objective C.”Please Read 3rd Question its important one.”

Questions are provided in sequence so please give answers in sequence as its understandable to me and others.

Question 1
I have two classes derived from NSObject: A and B:

@interface A : NSObject 
@end                               

@interface B : NSobject
-(void)display; // It displays "I am class B"
@end

Now if I do this:

A *a = [[B alloc]init]; // Show warning not error (it must be illegal)
[a display];            // prints "I am class B"

It calls the display method of class B. I don’t think that it should happen because:

1. A doesn’t have the method display. By polymorphism.

2. This could be a security threat as I am creating reference of any class and passing object of any another class and accessing data by it.

3. There could be design issues as Dog class instance gets an object of Printer class and now i am calling print method on Dog instance.

4. I have reference of NSArray and passed object of NSMutableArray and now i am calling NSMutableArray method on this instance.

   [nsarr addObject:@:abc]; //Looking very odd

Question 2
If I have Foo protocol and if any class is not confirming it. It should not be allowed to get object of that class in protocol reference.

@protocol Foo
@required
-(void)abc;
@end    

If i call:

id<Foo> obj= [[B alloc]init]; // Shows warning ignore it for now as it must be illegal also
[obj display];                // It will call display method which should be illegal  

1. It should not happen, as B is not conforming to protocol Foo and obj is taking B object and calling B instance method. I think its very bad because of polymorphism and security

Question 3
If my class has a class method which returns an object of that class which is not autoreleased, the compiler shows warning. If I pass the object returned by that class (not conforming protocol) method to reference of protocol. (IT SHOULD BE AN ERROR).

id<Foo> obj = [Abc aClassMethodReturnsObjectWhichNotAutoreleased]; //show warning

It shows a warning which is good. Abc did not conform to the protocol Foo

BUT

id<Foo> obj = [NSArray arrayWithObjects:@"abc",@"def",nil]; // It does **not** show a warning as it will return autorelease object. NSArray doesn't conform protocol Foo

Why does the above assignment to the NSArray class not show a warning as it is showing in the previous example.

Thanks in advance.

EDIT

*Answer 3rd Question:*As NSArray returns id object which will allow to pass in “id obj” but in “aClassMethodReturnsObjectWhichNotAutoreleased” case the method returns “ABC *” pointer so that is why compiler giving warning in this case.

Answer 1

Question 1:

A *a = [[B alloc]init]; //Show warning not error (it must be illegal)
[a display];  //prints "I am class B"

Here you are using a static type A for the variable named a. You are then assigning a different type of object (B) to the variable.

Unlike java, Objective-C does not enforce the static typing requirement, however it does warn you when it is being compiled since the compiler detected a difference between the declared type and the actual type of the object. It happily stuffs the B object into your variable though, so a is now pointing to the B object that you created. Once the program is compiled and running (at run-time), A *a is treated the same as id a.

Another feature of Objective-C is that you can send any message to any object at any time. This is part of the dynamic nature of Objective-C. Obviously there are cases where sending the wrong message to an object can cause bad things ™ to happen so you need to ensure that you only send appropriate messages. There are various functions that can test the class of an object at run-time, or even test to see if it is able to handle a particular message before you send it in order to prevent the bad things. If you are using static typing (like in this example) then the compiler will issue warnings to tell you that you may have made a mistake and should review the code.

Question 2:

This is actually very similar to question 1. The compiler is warning you that you are assigning what appears to be an incorrect value to the variable, however at run-time you can send any message to any object, so it will work on the actual object instead of the “expected” object from the type declaration.

Question 3:

Good question. I would have thought that you would get a warning there too. Maybe someone else can help out on that. My first thought is that this is a bug and should be reported as such, but there may be a reason for it that I’m not aware of….