On Fri, 23 Jan 1998, Emmanuel BEUQUE wrote:
> À (At) 16:21 +0000 22/01/98, Xavier MARIE écrivait (wrote) :
> I understand that this may be a problem for an engine. While an event is
> only generated at a time and checked immediately, several link effects
> could have been added to the execution queue, E.G. a link effect action can
> fire another link.
>
> I think that programmers of engine would consequently ask for some
> restrictions, for instance, the following one :
>
> "GetLastEventData only returns the eventData associated with the last
> generated event. It should generally be called as the first elementary
> action of the linkEffect in order to prevent other link to be fired before
> its evaluation. The author should also be aware of possible side effects if
> several links may fire on the same event."
I think it should read:
"GetLastEventData returns the associated eventData for the currently
processed event."
There is the possibility that the currently processed event is _not_ the last
one generated. The GetLastEventData action does only make sense if I can get
the eventData for the current event.
I don't think that it complicates implementations. You have to store the
eventData for the comparison of the eventData and the associated eventData
anyway.
Andreas
-- o _ Andreas Kraft (\_|_) GMD FOKUS, kraft@fokus.gmd.de, +49 30 3463-7232 T> ] [ The sky is the limit