On Thu, 1 Jul 2004 07:19:18 +1000, Andrew Scott <[EMAIL PROTECTED]> wrote: > Ok maybe this example would be better for you
Nope. > I don't need to do encapsulation here, and again this one of many examples > in our framework were I don't need to worry about it... My choice not yours, And here we agree. It is *your* choice. And it is my choice to recommend folks don't use "this" scope under any circumstances. You missed a point I made earlier even tho' you actually confirm it here: > Like I said I understand the risks and the > dangers and it is all taking into consideration when I design my component. *You* may understand but a newbie won't necessarily. And newbies tend to see code and just run with it. If there is a sense that "this" scope is 'good', newbies will program that way and then be very confused when everyone starts telling them their code is crap. All I'm trying to do is ensure that folks see "this" scope as a very rare exception. And if you were writing code in Macromedia, you wouldn't be using "this" scope even in the examples you gave - you'd add get/set methods and use "variables" scope. And that's our choice :) Pretty much every coding standard for every OO language prohibits the use of public data members - to preserve encapsulation - a term that any newbie going anywhere near OO needs to learn and understand. --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
