|
Or, just a thought, you could use a goal-oriented approach such that
the first CE of the rule is a Goal object with a Name, usually a
literal equal to a integer for speed considerations and to avoid the
String.equals(String) method. All of the rules having to do with one
stage would ask "if the goal is xxx" and CE1 and CE2 THEN AE1 and AE2.
Remember, the rule in one set of goals could set another goal if
necessary and, when finished, the rules would return to the calling set
of goals. For this you would need depth first, meaning that the last
activated goal would be the first on the agenda table. I've used this
quite a number of times fairly successfully without having to resort to
priorities. BTW, in answer to the earlier question, most treatise on the subject of rulebased systems say something like, "If more than three levels of priority are needed this probably indicates that a procedural program would be better fitted for the solution to the problem." I know that the Girratano and Riley book has this statement as well as the Cooper and Wogrin book. I usually insert a Goal named "Start" where Start is a static final int = 0. Other goals could do different things and you would not have break things into rulesets to accomplish this. SDG jco Jason Morris wrote: I think that Ross Judson said: |
- JESS: hi All Subrahmanyam
- RE: JESS: hi All Mitch Christensen
- RE: JESS: hi All remco . radstaak
- RE: JESS: hi All Judson, Ross
- RE: JESS: hi All Jason Morris
- James Owen
