While this may sound like a whining session, I really do have a wish for the list:
I would like to see JESS have an alternate language (JESS++) that is focused on the object-oriented nature of the Java language. I would assume that all the features of JESS could be incorporated into JESS++ without an enormous amount of pain. Many of the other rule "languages" use simply state the positive or negative existence of objects in the working memory and then use Java methods to perform the conditional tests and actions. Of course, they also use some "home brewed" extensions to perform operations that are really enhancements to the fundmental rule operations. I would hesitate to speak on the conjunctive/disjunctive aspects of the language and defer to the JESS author. My feeling (from using JESS) is that the Lisp-like syntax induces an impedance mismatch between the statement of the problem and the object-oriented nature of the solution (if one focuses directly on an O-O solution). If the core pieces of JESS were used as the foundation of JESS++, I would think that a new (more O-O) JESS++ language could be constructed (using something like YACC) and then the core JESS code could be used in the parser actions to produce exactly the same result as the original JESS language. JESS seems to be positioned in the middle of the pricing scale which makes it very affordable for rules projects and if JESS++ were possible, it may enhance the usability of the product by programmers who do not abide with the "rules gods" (just common folks like us). -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
