Michael Neale <michael.neale <at> gmail.com> writes:
Hi Michael,
Thanks.. and sorry for this late follow through..
I want to discuss two things:
1. Creating workingMemory instances every time is working out fine. This is how
I approached it first, but got mislead thinking that WorkingMemory is expensive
to create. And *when* it makes sense to keep the working memory is, out of a set
of facts if a small no of facts change between firings. This is because Agenda
re-validation takes place everytime facts are asserted or retracted. Please
correct me if I am wrong..
2. In my original post, I think I put too many points that it is confusing. Let
me list down the points here:
a. Null facts when asserted cannot have any effect on agenda. So,
should it be
failed right when asserting the object. This early failing I feel will speed up
development and reduce runtime surprizes.
b. PrimitiveLongMap I think has a bug. It reflests in
WorkingMemoryImpl.getObject() too. containsKey() returns false for key that is
mapped to null. My original post lists its effects and proposed corrections.
Please check it out. Did I post in the wrong forum?.. If so, do we repost this
in the developer forum?..
Thanks again and Regards
prem
