I think Jonathan Sewall wrote: > My purpose would be far better served if there were simply a String or a > numeric member field of Activation and appropriate accessors by which I > could label the instance uniquely and identify it again later, after > deserialization. If I could effectively subclass Activation, I'd add > this myself.
In the absence of multifields, you could uniquely identify an Activation as a tuple containing the list of fact ids and the name of the rule. But as multifields can be matched multiple ways, this isn't necessarily unique. As far as the reordering goes: I agree that this isn't optimal. I'll look at the code and see if there isn't a better way of doing things that doesn't have this side-effect. --------------------------------------------------------- Ernest Friedman-Hill Advanced Software Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 -------------------------------------------------------------------- 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] --------------------------------------------------------------------
