Re: new/update form patterns

Subject: Re: new/update form patterns
From: Christian Pekeler <email@hidden>
Date: Thu, 26 May 2005 14:22:18 -0600
Delivered-to: email@hidden
Delivered-to: email@hidden

I'm just kind of curious if the community-at-large agrees on what is "right". Begin religious debate .......... NOW.

The Java naming convention states "The terms get/set must be used where an attribute is accessed directly". In my opinion, this convention breaks encapsulation/information hiding because I would need to change the method name when changing the implementation (from returning a computed result to returning an attribute, for example). That's why I almost never use the get prefix in my own code.

Christian

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >new/update form patterns (From: Mike Schrag <email@hidden>)
  >Re: new/update form patterns (From: Kaj Hejer <email@hidden>)
  >Re: new/update form patterns (From: Mike Schrag <email@hidden>)




Prev by Date:
Newbie: WOComponent doesn't appear

Next by Date:
Re: new/update form patterns

Previous by thread:
Re: new/update form patterns

Next by thread:
Re: new/update form patterns

Index(es):

Date
Thread













  
   Home
   Archives
   Terms/Conditions
   Contact
   RSS
   Lists
   About
 






Visit the Apple Store online or at retail locations.

1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2011 Apple Inc. All rights reserved.

References:
	>new/update form patterns (From: Mike Schrag <email@hidden>)
	>Re: new/update form patterns (From: Kaj Hejer <email@hidden>)
	>Re: new/update form patterns (From: Mike Schrag <email@hidden>)