You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/.../RHAddressBook/RHAddressBookSharedServices.m:122:13: Comparison of function 'ABAddressBookCreateWithOptions' not equal to a null pointer is always true
this comes from such blocks as:
#if __IPHONE_OS_VERSION_MAX_ALLOWED >= 60000
if (ABAddressBookCreateWithOptions != NULL){
...
#endif
it offers Fix-It solution
#if __IPHONE_OS_VERSION_MAX_ALLOWED >= 60000
if (&ABAddressBookCreateWithOptions != NULL){
...
#endif
I.e. to use reference to the method.
(and there are about 10-15 issues like that)
Actually I'm quite confused, I think XCode fix is not correct:
Thise comparisons are made to check availability of the functions, so it's correct that in target environment (iOS6+), this will be always true (methods presented). But it might be different on different environment (though still during compilation it will probably generate the same optimization - always false).
But I don't want to have open issues in my project, using of '&' in front of the method name still will work on iOS6+ - it refers to allocation of the method in method allocation table (or whatever) and it won't be NULL. But I have no idea if this will be issue (not for me) on iOS < 6.
Anyone advice?
The text was updated successfully, but these errors were encountered:
/.../RHAddressBook/RHAddressBookSharedServices.m:122:13: Comparison of function 'ABAddressBookCreateWithOptions' not equal to a null pointer is always true
this comes from such blocks as:
it offers Fix-It solution
I.e. to use reference to the method.
(and there are about 10-15 issues like that)
Actually I'm quite confused, I think XCode fix is not correct:
Thise comparisons are made to check availability of the functions, so it's correct that in target environment (iOS6+), this will be always true (methods presented). But it might be different on different environment (though still during compilation it will probably generate the same optimization - always false).
But I don't want to have open issues in my project, using of '&' in front of the method name still will work on iOS6+ - it refers to allocation of the method in method allocation table (or whatever) and it won't be NULL. But I have no idea if this will be issue (not for me) on iOS < 6.
Anyone advice?
The text was updated successfully, but these errors were encountered: