Re: var watcher behaviour

Hm, it seems now clearer to me and to be no error: my modifying timer did
this:

- it incremented the variable by the ++ operator: one read, one write: 2
accesses;
- it compared the variable with a number: 1 read access.

So there were three access events (poll was set to "rw"). Ok, one has to be
very carefully here. (Or to temporarily disable the associated watcher - but
how can I get all the watchers watching a certain variable? And what if it is
modified in code I cannot control?) Of course, fine granularity SHOULD be
available. So, hm ... I remember an optional "clumb" feature. What are you
thinking?

By the way, the sent script activated the var watcher four times, not only
three - what was the fourth event?

                        Jochen