RE: xPLHal scripting matches

[Kevin Hawkins]

I was just looking for a mechanism to choose whether to cease further
processing or to return to the place in the sequential matching and
continue...

- I hadn't anticipated any concurrency in the scripts ( multiple threads )
-
haven't really thought if that would be advantageous or complex, requiring
a
lock mechanism to guarantee the correct order of execution.

I felt that assuming all would run (sequentially) was a more natural
interpretation than that previous filters would pre-empt you.

Kevin



> -----Original Message-----
> From: Tony Tofts
> Sent: 10 September 2003 18:05
> Subject: RE: [ukha_xpl] xPLHal scripting matches
>
> > I'd prefer it to carry on processing, and maybe issue something
like:
> > sys.terminate() or sys.break() if you want it to not process
> > any more scripts.
> >
> > Tony - could this be done?
>
> Since we currently don't process any further scripts, a sys.break
would
> have
> no use?
>
> Are we saying xplhal should process all matches, launching multiple
> scripts
> for each message?
>
> Actually sys.break wouldn't work, since by the time it is called - the
> other
> scripts would already be in progress?
>
> Thoughts?
>
> Thanks
> Tony
>