On Feb 9, 2006, at 12:33 PM, Jerry W. Walker wrote:
Like Chuck, I tend to use straight assignment for many of the same reasons. However, in this example I just didn't want to make arbitrary decisions on whether the members whose values I was setting were iVars or methods.
Does it bother anyone else that WOBuilder generates protected rather than private ivars so that WO can access these ivars directly rather than using accessor methods? Seems like a bad practice to me.
Instead, I make all my ivars private forcing WO to access them via accessor methods unless there's a good reason to make these ivars accessible to subclasses (but then they should probably use accessor methods also).
Aloha, Art _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
