Hi Folks,
Work progresses on Jess 7. I'm making a sweep through the code looking
at error messages, in particular looking for ones that are hard to
understand. I'd love it if people could help me by sharing small
snippets of code that evoke Jess error messages that don't make sense
or seem inappro
I don't have a code example here, but to me the most difficult error message is the
one
that happens when a function that is part of a pattern (LHS) is called which produces
an
error.
Since the pattern is evaluated when an assert or modify is executed by another rule's
RHS, the error message
Hi,
Is there any ant tool which can check the syntax in clip files?
Thanks
Bhaskar
To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]'
in the BODY of a message to [EMAIL PROTECTED], NOT to the list
(use
Title: RE: JESS: Least favorite error messages
The worst error message is a silent failure...
Here's one:
Given a java class named "Disbelief" with a boolean property called "really":
(defrule jess-rules
(Disbelief (really FASLE))
=>
)
The parser doesn't detect that the misspelled F
Title: RE: JESS: ant task for checking rule file syntax
If your script to be checked does not call (run) or (run-until-halt) and contains primarily deffunction/defquery/defrule statements you can try:
disclaimer: not tested...
All this does is run jess
I think John Aronson wrote:
> The profiler reports that that almost all the execution time is spent
> loading classes. I'm hoping that fact means that there's something wrong
> with my code which I could fix to improve the performance.
It does look like a lot of time is being spent loading classe
Thanks for the response. The class loading time wasn't a one time
thing, it was a constant drag when I was running from 100 up to 1 reps.
10,000 reps was taking over an hour so I didn't run that one a lot ;)
I did solve the problem though. I found that it was a lot faster to use
Jes
Title: RE: JESS: Optimization Question
Also, the following *might* be even faster - TBD:
(defrule prevent-logout
(ActionForward (path ?url&:(neq (str-index "Logout.do" ?url) FALSE)))
=>
)
You can move the _expression_ in the (test) up into the pattern if your _expression_ doesn't depend
