> That looks like it'd slow things down a lot - and be a > pain to type.
Not really. The comparison takes a millisecond or two, and it's only used in private methods. Typing is easy--type it once, and copy and paste. > And it could easily be got around: > > behav.mGetData(behav) > > I don't think there's a simple code method to enforce it. Fair enough. Like I said, it's not foolproof--in fact, that's exactly where it fails. It would be nice if Lingo had true private methods and properties. Then people like you and I wouldn't need to come up with workarounds. Your method of privatization looks like it would work as well as the one I proposed. Of course, neither is foolproof. The best we can do is to make people think twice, or three times, before they access a private method. Or, if you're so inclined, you could, as a team leader, see who is breaking encapsulization and go by their cubicle and bludgeon them into submission. Works better with dogs than cats. Cordially, Kerry Thompson [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/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!]
