Custom Properties

[Dick Kriesel]

On 4/12/06 6:13 PM, "Mark Wieder" <mwieder at ahsoftware.net> wrote:

> Dan-
> 
> Wednesday, April 12, 2006, 2:49:17 PM, you wrote:
> 
>> One important use of setProp in particular comes into play when you create a
>> library that has values you don't want outside programs/users to change. You
>> just set up a setProp handler that politely, silently or rudely refuses to
>> set the property's value. This is an important idea in object-oriented
>> design.
> 
> On first thought, that sounds like an interesting concept. On second
> thought, it seems like a better case for script-local variables in the
> library stack. How do you separate out a "set" command coming from
> outside the stack from one generated locally?

How about applying the executionContexts?

setProp uFoo pValue
  if word -1 of item 1 of line -2 of the executionContexts = \
      word -1 of long id of me then
    -- set the value and trigger the consequences
  else
    -- refuse
  end if
end uFoo

-- Dick