The analysis tool would be good for some of this. But it is for static
analysts. This sounds like it could be a runtime tool that optionalls
detects and stops it. Very handy.
Sent from my iPhone
On 09/12/2007, at 23:08, Darko IVANCAN <ivancan(a)gmx.de> wrote:
Hi Mark,
Should this be an (a) off-line or an (b) on-line tool ?
(a) off-line: parse rule file and point out the lines/rules which
could
lead to a potential recursion
(b) on-line: identifiy a potential recursion while runtime by
observing
the agenda and the working memory
Sounds like fun indeed, ... I'll take a look once I have some time,
Darko Ivancan
On 09/12/2007 08:41, Mark Proctor wrote:
> I've been getting requests for a testing tool that checks for
> recursion, and exits the test if its detected. Any takers fancy
> having
> a go at this? Mostly its just an event model thing, bit like the
> audit
> view. But as recursion is not just about rule recursion, but
> Activation recursion too (i.e. rule recursion with the same data),
> you'll need to create a stack of rules and tuples, and check against
> that stack for possible recursions. Should be fun :)
>
> Mark
> _______________________________________________
> rules-dev mailing list
> rules-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/rules-dev
>
>
_______________________________________________
rules-dev mailing list
rules-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-dev