>I do not agree with BindEvents, for it will mean that you are relying in some external object to do a job that it was supposed to be taken care of internally, unless you meant to have bindevent in the same object (something like bindevent(this, 'SomeProperty', this, 'SomeMethod')) which looks completely unnecessary

*Any* technique that protects the value is better than none at all.

>>I don't think we're disagreeing at all. A completely open property is no better than a public variable unless/until one uses the bindevent, access/assign or get/set to protect a property against code problems. :)