I think Timothy Redmond wrote: > > But it isn't obvious to me why the rule was so bad. I constructed a > small experiment. It appears that Jess is not as efficient if it has > a rule where a java object is getting matched with another java object.
OK, I remember now what's going on here. The problem is that the hashCode() of some Java objects (Collections are one famous offender) can change, meaning that the method isn't really available for use in indexing. To be safe, later versions of Jess 6 simply don't do indexing on Java object fields -- better slow and correct than fast and wrong! Jess 7 will (eventually) have a scheme whereby you can tell Jess which of your classes have mutable hashCodes. Jess will know about many common cases, and you can provide additional information. This will let you have both correctness and speed. --------------------------------------------------------- Ernest Friedman-Hill Advanced Software Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- 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] --------------------------------------------------------------------
