Hi David,
I think David Young wrote:
>
> Sigh. The behavior of (definstance) in 4.1b4 has changed, hasn't it? I
> see from the documentation a couple of conflicting statements:
>
> * Section 3 Jess Function Guide
> (retract): Retracting a definstance fact will result in an
> implicit call to undefinstance for the corresponding object (the
> object will no longer be pattern-matched.)
>
> * Section 7.7.2
> "Once a definstance construct has been issued, there will always
> be a fact on the fact-list representing that object (until the
> 'clear' command is issued.)"
No, this is just an oversight in the documentation. (retract) and
(undefinstance) should both still work, and they should leave no trace
of a previously matched object. There's no reason why you
shouldn't beable to re-definstance an object. I have your example, and
I will be looking into it. Hopefully I can clear this up quickly.
> I suppose I could work around this issue by not using
> 'defclass/definstance' and writing my own "shadow" deftemplates, but
> gosh...
>
> Any clarification would be appreciated. Thanks much.
>
> Regards,
---------------------------------------------------------
Ernest Friedman-Hill
Distributed Systems Research Phone: (510) 294-2154
Sandia National Labs FAX: (510) 294-2234
Org. 8920, MS 9214 [EMAIL PROTECTED]
PO Box 969 http://herzberg.ca.sandia.gov
Livermore, CA 94550
---------------------------------------------------------------------
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the
list. List problems? Notify [EMAIL PROTECTED]
---------------------------------------------------------------------
