Change the way of calling function objc_msgSend().
Motivation and Context
Unstrict usage of objc_sendMsg is deprecated since Xcode 6.
Of course, it is able to be fixed if the user builds the option 'Enable strict checking of objc_msgSend Calls' at the Xcode from yes to no.
However, this project is not an Xcode project, so there's no way to turn that option off.
So this pull request improves the way to call function objc_msgSend().
How Has This Been Tested?
If you try to build it on the original source, you'll see that the compiler prints the error and stop compiling, saying "Too many arguments".
But if you try it with my source, you'll see that no error occurs, with 100% of compile.
Screenshots (if appropriate):
Types of changes
[ x ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[ x ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
Djiit
commented
4 years ago
Description
Change the way of calling function objc_msgSend().
Motivation and Context
Unstrict usage of objc_sendMsg is deprecated since Xcode 6. Of course, it is able to be fixed if the user builds the option 'Enable strict checking of objc_msgSend Calls' at the Xcode from yes to no. However, this project is not an Xcode project, so there's no way to turn that option off. So this pull request improves the way to call function objc_msgSend().
How Has This Been Tested?
If you try to build it on the original source, you'll see that the compiler prints the error and stop compiling, saying "Too many arguments". But if you try it with my source, you'll see that no error occurs, with 100% of compile.
Screenshots (if appropriate):
Types of changes
Checklist: