The runtime won't generate this warning if the selector has no type information
(selectors returned by @selector() are untyped, for example). If it comes from
nib loading, then it sounds like we're creating the selector the wrong way. We
should be calling sel_registerName(), which will give
When decoding actions we call, NSSelectorFromString() and this
internally uses sel_registerName(). According to your mail this is the
right way to do it even for clang.
You talk about a wrong way to generate selectors, could you explain what
that would be?
Fred
On 29.01.2012 12:54, David
This sounds correct. I believe that sel_registerName() may return a typed
selector if there is only one selector registered for a specific type - this
may happen if it is called when the runtime has only loaded the class with the
wrong type encoding, and not the one with the correct one. I
Hi,
still with AddressManager, I recognized when I edit a text input field, the
console gets spammed with:
Calling [NSTextView -copy:] with incorrect signature. Method has v12@0:4@8,
selector has @12@0:4@8
Calling [NSTextView -paste:] with incorrect signature. Method has v12@0:4@8,
selector
Hi Sebastian,
If you put a breakpoint on objc_selector_type_mismatch, you will enter the
debugger whenever this is warning will be printed.
On 28 Jan 2012, at 13:17, Sebastian Reitenbach wrote:
Method has v12@0:4@8, selector has @12@0:4@8
This looks potentially dangerous. The caller is
On Saturday, January 28, 2012 14:44 CET, David Chisnall thera...@sucs.org
wrote:
Hi Sebastian,
If you put a breakpoint on objc_selector_type_mismatch, you will enter the
debugger whenever this is warning will be printed.
OK, so I did (actually it did not picked it up, so I set a
On 28.01.2012 17:44, Sebastian Reitenbach wrote:
On Saturday, January 28, 2012 14:44 CET, David Chisnallthera...@sucs.org
wrote:
Hi Sebastian,
If you put a breakpoint on objc_selector_type_mismatch, you will enter the
debugger whenever this is warning will be printed.
OK, so I did
Hi,
Based on Sebastain's bactrace, I think it's a spurious warning: the method
isn't actually being called with an incorrect signature, the menu update code
is just calling class_respondsToSelector() to check if an object responds to
the selector copy:. The selector being passed probably comes
