> Writing a lot of redundant handlers is almost always 'pure OOP'. I
> think the meaning of not accessing the properties directly is that
> you will be allowed to change the inner workings of the script a lot
> without changing in any of the calling handlers.
I can begin to see the outlines of the reasoning. Thanks for everyones
input.
I guess you could cut redundancy with a string of "public" properties:
on getProperty me, prop
propString = "prop1, prop2"
if propString contains prop
return value(prop)
else
alert "Private property - no trespassing"
end if
end
This would work if one adhered to ones "own" rules for sprite access.
But I still wonder what's the fuss...
Oh well, maybe I'll get it one day.
-Clars
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
