change from
Rete.modify is slower than a retract, Fact.setSlotValue, assert.
I would vote for keeping the 6.1 behavior from the modify command,
exposing the internal modify to Rete and Java, and doing a collection of
slots for the change notification.
Thanks,
Jon Weygandt
-Original Message
Jess,
Not sure if this is known, have not seen much on the internal workings
of modify. I'm concerned about this because it looks like modifying a
fact sometimes requires the equivalent of:
For each slot modified
{
Retract the fact
Set the slot
Assert the fact
}
Although in 6.1p7 it
Jess,
An area of somewhat unclear documentation about how Basic Patterns are
interpreted, and I want to be sure before passing information on to our
customers. I have the following rule, pay attention to the TRANS_STATE
slot:
(defrule FC
?cast -
(FC
(SQL_OPERATION UPDATE | INSERT)
: Re: JESS: How does the pattern match: ?trans_state SI |MI
| EI
I think Jon Weygandt wrote:
Jess,
That's her picture on the cover of Jess in Action :)
(TRANS_STATE ?trans_state SI | MI | EI)
My procedural view would be the pattern is evaluated as:
(TRANS_STATE (?trans_state SI
)
(fact-slot-value ?eqpst S2)))
(test (neq (fact-slot-value ?eqpst S3)
(fact-slot-value ?eqpst S4)))
)
)
...
=
...
)
Thanks,
Jon Weygandt
-- Original Message --
If one thread is executing run
