Or just go with this safe rule: Make everything private first and allow public access as needed
If you need to expose private data to the public, use an accessor to retrieve it. I would not recommend just any process to use use the "this" scope. Only time "this" is functional is when returning instances of an object in your init() methods. Teddy On 11/16/06, Ian Skinner <[EMAIL PROTECTED]> wrote: > > A lot of people will say "NEVER" use the 'this' scope. But I say if one > understands the differences between the 'variables' scope and the 'this' > scope (how the former is private and the latter is public) and code > accordingly, I say it is a development choice on which scope one uses. > > > -------------- > Ian Skinner > Web Programmer > BloodSource > www.BloodSource.org > Sacramento, CA > > --------- > | 1 | | > --------- Binary Soduko > | | | > --------- > > "C code. C code run. Run code run. Please!" > - Cynthia Dunning > > Confidentiality Notice: This message including any > attachments is for the sole use of the intended > recipient(s) and may contain confidential and privileged > information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the > intended recipient, please contact the sender and > delete any copies of this message. > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:260725 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
