macOS Any use for undeclared @implementations?

Most often you see this used for overrides (methods prototyped by a superclass, like -init or -mouseDown), for protocol implementation (like NSCoding or datasource, implicitly prototyped via the protocol conformance declaration) and for delegate methods. Occaisionally you might see non-prototyped methods that are only used within the implementation, which the programmer might do in order to hide the methods, but this is a generally discouraged practice.

zippyfly said:

But of course! (Smacks forehead. Mine, not yours. ;-)

Click to expand...

I recommend to set up your projects so that all compiler warnings are treated as errors, then make use of unknown selector a warning. (Especially useful when you write @selector(thismethod) instead of @selector(thismethod: ) )

I tend to have something like

@interface myclass (privatebits)
...
@end

in my implementation files for internally used methods so that these methods are not even visible in the header file.