| vitick@gmail.com 2008-03-28, 7:30 pm |
| On Mar 28, 12:38 pm, Uwe Klein <uwe_klein_habertw...@t-online.de>
wrote:
> vit...@gmail.com wrote:
>
>
>
>
>
>
>
> Always at your service, Sir!
>
> Well, there are a couple of issues:
> vwait stacks, it does not work in parallel.
> i.e any stacked vwait has to trigger to expose
> the underlying vwaits.
> This is an unpleasant situation at best.
>
> Vwait works on variable change. Thus your
> code sequence should never get further than the
> entry to [vwait]
> after $after_time [list set wait_var]
> next: you are vwaiting inside of a proc
> on a variable change in local scope.
> ( no upvar, nor global statement )
> but [after] expedites its payload in global scope
> and your script only reads that var anyway.
> ( imho you should get a background error on this )
>
> I am not clear how this works. But my guess is not
> in the way you think it works.
>
> On the other hand: I may be compleately wrong ;-)
>
> uwe
Thanks Uwe,
You are right about stacking of vwaits. But they do seem to work on
local variables.
I was so excited about it. But it turns out that only ONE such code
instance will actually run alongside the regular file events. If I add
another one, one of them will suspend until the first one finishes.
Well, back to reality. At least I learned something new today. Thanks
again.
|