EvgenyKarkan
commented
10 years ago Absolutely agreed with you! As i mentioned on Important note on READ.me - the main idea is not to re-use Cocoa APIs for CS algo-stuff. I think the more interesting way is to implement CS stuff by the "hard" way. So we thus can understand - what is under the hood of algo is? IMHO The naming conventions provided by you - is OK for me. :)
PS If you don't mind - all the code that you will provide, I will "uncrustify" with my settings. The main aim is - code style/conventions consistency. ok?
stanislaw
The changed proposed #14 is good but only partially - it is good to know that Apple's
reverseObjectEnumeratordoes its job - and as of Apple recommends to "use highest API possible" - it would be a better choice than to implement it by hands, but I think it would still be great to have both variant of methods to be kept in EKAlgorithms.What I suggest is to keep both methods side by side, the only trick is again to invent a good convention to handle this:
My initial thought was something like:
or
But I personally dislike using underscores in method names that is why I also thought about something like
For now I think that "CocoaImplementation_reversedArrayWithArray" is the best naming convention to be used for methods showing usage of highest-level of API suggested by Cocoa.
Let me know what you think.
Here are more examples we could write using Cocoa API:
Index of maximum element:
[array valueForKeyPath:@"@max.integerValue"]Binary search from awesome objc.io Issue n7, Binary Search.