The order in which rules fire is obviously irrelevant if that order does
not affect the behaviour of the program. I discovered that the order in
which rules are defined affects program behaviour because I was
unknowingly trying to assert the same working memory element twice.
This I now
I tried to have two definstance calls on the same Java class. Specifically,
(defclass market Market)
(defclass agent TradingAgent)
(defclass producer TradingAgent)
Instances of class Market have two public members: agentsList and
producersList where the latter is a subset of the former.
[EMAIL PROTECTED] wrote:
If the defrules are ordered as above, then no shadow facts are created
for producer. If the producers rule is defined first, then three
producers shadowfacts are created followed by seven agents shadow facts.
Is it the case that there cannot be two points to a
I think Scott Moss wrote:
The order in which rules are fired depends first on the conflict
resolution strategy, but if two rules are of equal priority by that
criterion, then they'll fire in an arbitrary order that just falls out
of the Rete network implementation. That order is affected by,
