When should they be used and when is it unnecessary to add them? I've been coding all my properties to only be accessible via getter/setter...but are there instances where u should just make them public vars? i.e. this scope
As Dave said, there's a great discussion in the archives. The bottom line is there is never a situation where 'this' scope is the preferred way. The question you need to ask yourself is why do other objects need access to your data? Yes, there are times when you need to expose some of an object's data but if an object encapsulates all of its behavior properly, most operations should be doable without handing out data (except at the boundaries between sub-systems where you need memento and/or data transfer objects).
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive." -- Margaret Atwood
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
