Sean, If its bad why do MM allow it to be used, why do macromedia allow for these problems?
Anyway I guess what I am saying is that from a developers point of view, if the concept is bad then why put it there in the first place? There are instances where it is a good idea to use the this scope, and then there are times when it can be very bad. I would like to say that this is the same with most OO languages I have seen so far. But to just turn around and say its bad and don't use it, means nothing to most who don't understand why it is there in the first place. Maybe a bit more documentation and clearly explain why you shouldn't use it and when it is safe to use it would be better. Regards Andrew Scott Technical Consultant NuSphere Pty Ltd Level 2/33 Bank Street South Melbourne, Victoria, 3205 Phone: 03 9686 0485 - Fax: 03 9699 7976 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sean Corfield Sent: Tuesday, 29 June 2004 2:05 PM To: CFAussie Mailing List Subject: [cfaussie] RE: this ----- Original Message ----- From: Stephen Milligan <[EMAIL PROTECTED]> I'm pretty sure if Hal was around he'd be chirping up around now to tell you that using the 'this' scope for storing instance data is a bad thing. Since Hal isn't on this list but I do know his position on this, I'll speak for him: "Don't use 'this' scope!" --- 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/ --- 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/
