Up until now I've been using -[NSValue valueWithPointer:] to store the addresses of selectors in an array. Sometimes I want to store the lack of a selector so have been using [NSValue valueWithPointer:NULL]. In the 10.11 SDK this now gives a "Null passed to a callee that requires a non-null argument" warning.
So is the header for NSValue wrong in saying it requires a non-null argument, or should I update my code to maybe use an NSNull instead (which is a bit of a pain when it comes to unwrapping, but not hard).
BTW - valeWithPointer is quite happy to create a value with null and correctly gets round-tripped when calling [NSValue pointerValue] on it (i,e it comes back as NULL.