Do you think it is a bad idea to completely defy Objective-C getter conventions by defining a getter method such as origin as getOrigin instead? I really don't like the idea of just writing "origin" for a getter method because it makes it look too much like an instance/class variable and I feel like it makes much more sense to do it my way.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Objective-C Programming Conventions
- Thread starter coolbeans777
- Start date
- Sort by reaction score
Use properties, then you don't need to write an accessor yourself, @synthesize will handle it. If you must you can then write a getX method that uses the accessor (or I guess accesses the property directly). If you choose only to implement getX accessors you won't be key-value compliant, you won't be able to use dot-property syntax, and other people using your class will be confused. Why do you want to type more and be specifically unusual compared to existing code? You're going to have to be used to it to use other frameworks anyway, you may as well just do it "right" in your own code.
-Lee
-Lee
You can define your own property accessor names by using the getter and setter attributes of any property.
Code:
@property (getter=gimmeThatFoo, setter=stuffThisIntoFooNow:) fooType foo;
