Ah I see. Not that I am aware of, in fact if you require a set
property in your object then init is the best place for it to be.
Sent from my iPhone
On May 20, 2010, at 9:47 AM, Thomas Davie <tom.da...@gmail.com> wrote:
On 20 May 2010, at 15:45, Barry Skidmore wrote:
If you need to have it set you should create an initWithOptionName:
and call that from your standard init, or return an error stating a
missing value is needed.
Your init should always call down tithe most specific init.
Specific examples of this are available as best practice in several
cocoa and design pattern books.
I think you've misunderstood what I was asking.
If I use a setter (in the most specific init), then I don't need to
recode (even the most specific init) if I change how the property is
implemented.
If I don't use the setter, I do.
What I was asking was why you would want to avoid using setters in
the init method... Is there some safety issue I've missed?
Bob
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
