Hi Jon
>From a "purist" view, you should never access or set the property of another
object without using a get/set function call. If you break from a "purist"
standpoint on the access you stand the chance that your code will completely
blow apart if someone is stupid and changes the name of a property later
(for some strange reason). At least if the code is in the actual object and
is accessed via a get handler, the debug window would give someone the
option of seeing what the property names are for an object while inspecting
the set method that is exploding. Such liberty is not granted via direct
access, it just gives a nice error of property not found #someProperty and
you don't have access to visualize the object's properties as you would if
the get method was called and the property not found #someProperty error
showed up.
Never ever ever set a property outside of the object itself (ie a set
handler), if you do then its a free for all in the back ally to figure out
where the heck the problem arose from, especially if your project is fairly
complicated.
So keep it encapsulated within the object, don't deviate especially if you
are going to hand this code base off to some other poor sap to maintain.
Sincerely
Mark
--------------------------------------------
Mark R. Jonkman
Mark R. Jonkman Consulting
ADDRESS: 20 Windermere Crt., Guelph, ON, CANADA N1E 3L4
PHONE: 519-837-8509
EMAIL: [EMAIL PROTECTED]
--------------------------------------------
[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!]
