Is the only Jess requirement for a Java class to be a "value class" that it have an immutable hashCode? (i.e., immutable for the JVM's life?)
Or is there a deeper requirement that all the component values affecting an equals comparison between two instances of the class are immutable as well? Intuitively, a "value class" would seem to be more restrictive than mere hash equivalence. Ref http://herzberg.ca.sandia.gov/jess/docs/71/functions.html#set-nonvalue-class - Mike Smith -------------------------------------------------------------------- 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] --------------------------------------------------------------------
