Home/ Questions/Q 8491381
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T22:24:25+00:00

What is the best practice for naming an Objective-C selector that doesn’t take parameters

  • 0

What is the best practice for naming an Objective-C selector that doesn’t take parameters but can return an Error?

Example (a method that gets soundtrack data from the web):

- (NSData*) soundtrackData:????? error:(NSError**)error;
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Apple uses one of two styles in the Cocoa frameworks:

    - (NSData *)soundtrackData:(NSError **)error;

    e.g. -[NSManagedObjectContext save:]

    - (NSData *)soundtrackDataAndReturnError:(NSError **)error;

    e.g. -[NSURL checkResourceIsReachableAndReturnError:

    It would seem that Apple is favouring the second style for new APIs these days, but either is acceptable. I like the conciseness of the first style, but the second does have a nice advantage that you can search for error: to find all methods in your code with error-handling.

    • 0