Not really. CFArray is basically the same as NSArray , you can even throw in between, this is called a free bridge .
CFArray (and its mutable copy) allows you to specify your own callback functions for saving and releasing objects (pointers) in your array, which allows you to store arbitrary pointers (not just NSObject s) in the array and implement your own memory management scheme, but I I doubt that this will lead to any real profit from productivity. For your use case, C arrays are probably the way to go.
source share