New answers tagged objective-c
Since Objective-C inherited its core object-oriented features (minus categories and protocols), including the syntax, from Smalltalk, there's obviously at least Smalltalk that has the same syntax. Plus, all of the Smalltalk descendants such as Self, Newspeak and Fancy.
So I have ran some simple tests myself. One that does something with the UI and one that calculates prime numbers in objective-c. After adding a swift file and calling a simple swift method from the objective-c code I measured the same tests again. There was no significant change in performance of the algorithms. I will conclude that there is no ...
Despite the other answers to this question, there is in fact a lot of behaviour in this method, and therefore a lot of things that could go wrong if we don't test them. Here are the cases I would check: When view is not empty and data is not empty, then both view and data are set in the Crashlytics object. This test is sufficient to get statement coverage. ...
The point of unit testing is testing your code's functionality in isolation. To the extent that your code is simply a wrapper around an external library, it doesn't really have any functionality to unit test. It may be useful to unit test the NULL and nil values, as you suggest. However, unit testing the call to the library doesn't seem worthwhile. ...
The preferred coding style would be (b) according to all style guides that I've seen (e.g. https://github.com/objc-zen/objc-zen-book#property-declaration). They recommend explicitly specify readwrite attribute (for the sake of clarity, I guess).
Top 50 recent answers are included