(and) does a short-circuited evaluation of its operands, but it is still a
single CE. Whether it returns false due to the first or second operand does
not matter: it'll have to be reevaluated over and over again.
Using two boolean functions in two different CEs may result in less
invocations of
r1 is fired, r1b is not (which is the desired behavior).
From: ejfr...@sandia.gov
To: jess-users@sandia.gov
Subject: Re: JESS: Time-varying methods inside a and in a test
Date: Mon, 18 Jul 2011 13:06:56 -0400
Although they do compile into different networks, the effect should be
It would be interesting to see these functions.
Basically I'm inclined to believe that this is not possible without some
weird side effect achieved by one of the functions.
-W
On 18 July 2011 19:42, Skeptic . skeptic2...@hotmail.com wrote:
r1 is fired, r1b is not (which is the desired
I¹ve read through the documentation, JESS in Action book, and mailing list
archive, and I can¹t seem to figure out this basic question:
How do I assert facts from Java into different modules (or
??contexts??)?
To be more specific, the application is a discrete event simulation with
Hi Russ,
Facts are assigned to modules at the template level, not at the individual fact
level. When you define a template using deftemplate, either the template
specifies its module by using a name like modulename::factname, or if the
name is unqualified, the template is placed in the current
