What is the difference between following delegate method call?

Question

I am confused about these delegate method calls.

Which one is the correct way of calling the delegate method?

@protocol XYZDelegate <NSObject>

@required
- (void)someMethod:(id)someObject;
@end

method 1:

- (void)someButtonAction:(UIButton *)sender {

    if([self.delegate && [self.delegate respondsToSelector:@selector(someMethod:)]]) {

    [self.delegate someMethod:sender];

    }

}

method 2:

- (void)someButtonAction:(UIButton *)sender {

    if([self.delegate && [self.delegate respondsToSelector:@selector(someMethod:)]]) {

    [self.delegate performSelector:@selector(someMethod:) withObject:sender];

    }

}

CMD K is how to fix formatting. Not the space bar or delete button. — Fogmeister, Sep 21 '16 at 14:19
Possible duplicate of [Using -performSelector: vs. just calling the method](http://stackoverflow.com/questions/1493125/using-performselector-vs-just-calling-the-method) — Kreiri, Sep 21 '16 at 14:21

Fogmeister · Accepted Answer · 2016-09-21T17:11:46.063

1

They are both pretty much the same. They will result in the same outcome.

The second is slightly less efficient.

What I would change is the line...

if([self.delegate && [self.delegate respondsToSelector:@selector(someMethod:)]]) {...

The method someMethod: is required by the protocol.

So you can remove it completely...

- (void)someButtonAction:(UIButton *)sender {
    [self.delegate someMethod:sender];    
}

And it will still work. You can send a message to nil and it just won't do anything. If the delegate is not nil then by definition it will respond to the selector.

If the delegate object does not conform to the method then you will get a compiler error (or maybe just a warning?).

Anyway, that should suffice.

Just as a side note. I personally prefer the first method and if there is more than one parameter then you would have to call it that way to be able to pass the parameters in corrcetly.

edited Sep 21 '16 at 17:11

answered Sep 21 '16 at 14:23

Fogmeister

76,236
42
207
306

1

i think its an compiler error as i found [here](https://developer.apple.com/reference/objectivec/1418956-nsobject/1418764-performselector) +1 for you .. – vaibhav Sep 21 '16 at 14:43
You don't need to check if the delegate property is non-nil. Sending a message on `nil` does nothing. – Avi Sep 21 '16 at 17:02
@Avi ah, yes. Of course. My head seems to be fully in Swift mode now, haha! :D – Fogmeister Sep 21 '16 at 17:03

score 0 · Answer 2 · answered Sep 21 '16 at 14:20

0

The difference is one calls the delegate method directly, while the other uses the runtime, through performSelector, to do so dynamically.

The latter is less efficient and pointless, but the results are the same.

answered Sep 21 '16 at 14:20

Avi

7,469
2
21
22

1

nowhere i found regarding runtime and compile time `performSelector` can you explain a bit more .. :) – vaibhav Sep 21 '16 at 14:45

What is the difference between following delegate method call?

2 Answers2