JESS: Minor bug in JessDE Editor

Hi, just wanted to let you know about a minor bug in the JessDE editor when marking the parentheses. In the example blow, when placing the cursor behind the closing parenthesis inside the string (M) then the editor marks the opening parenthesis in front of the strcat function. No big deal!

JESS: Using modules

I am using the Jess eclipse plug in 7.0a5 and the editor shows errors when using with multiple modules. Here an example: (defmodule MAIN) (deftemplate MainFact (slot childType) (slot id) ) (defrule MainRule1 ?rr - (Design::DesignFact (childType ?childType) (id ?id)) = (printout

Re: JESS: Using modules

Here we go ... I checked the error log and found the message: Attempt to redefine defmodule MAIN ... I removed this defmodule and it works. So I guess that addressing module MAIN means having a file with no defmodule, right? Felix [EMAIL PROTECTED] wrote: I think Felix H. Bachmann wrote:

JESS: JessDE and set-current-module

It seems that the syntax check in JessDE does not recognize the set-current-module statement. All definitions following this statement are still interpreted with whatever module was set before. This behavior is different from running Jess. There the definitions are treated as expected, meaning

JESS: Cascading errors

Just a suggestion ... So far in JessED when a file contains an error, then it seems that the whole file is marked buggy and all references in all files referring to the buggy file are marked as an error too, even if they don't depend on something that has an error. Here an example. Assume

Re: JESS: Cascading errors

CLIPS has the import and export statements that deal with this issue. That might also be a solution. Felix [EMAIL PROTECTED] wrote: I think Felix Bachmann wrote: Would it be possible to only mark something as an error if the dependent definition is wrong and not is something in the dependent

Re: JESS: XML and modules

I wanted to resend this message. Didn't get an answer so far. Can anyone please help? Felix Felix H. Bachmann wrote: I have some problems with the XML part of jess (jess70a6) I have a system that is composed of many modules which also have dependencies between them. When trying to convert a

Re: JESS: XML and modules

Great! thank you very much for the info Felix [EMAIL PROTECTED] wrote: I think Felix Bachmann wrote: [Charset iso-8859-1 unsupported, filtering to ASCII...] I wanted to resend this message. Didn't get an answer so far. Can anyone please help? Regarding file inclusion: the short answer

JESS: Retracting and asserting big sets of facts

Hi, To get the rule engine back to a previous state I want to retract and assert a set of facts. This is kind of similar to the Working Memory concept only that it is more fine grained. I have a Java function that handles the retract and assert, but found that it takes a long time to execute

JESS: Accumulate problem

regards Felix Bachmann - rule --- (defrule ImpactAnalysis::__AskcostOfChangeQuestion__ (declare (salience 500)) (MAIN::initial-fact) ?rr - (accumulate (bind ?res (create$)) (bind ?res (insert$ ?res 1 ?_20_own)) ?res

Re: JESS: Urgent gensym* question

Matt, I guess putting parentheses around (gensym*) would tell Jess to interpret it as a function and not as a symbol. I didn't try that with you example, but I am pretty sure it works. Felix Matthew J Hutchinson wrote: Hi everyone, In my .clp file I have used (setgen 1) to initialize the

JESS: Rule triggers on deleted fact

?res) id))) (parameters 0.2) (result nil Any idea? Felix Bachmann begin:vcard fn:Felix Bachmann n:Bachmann;Felix org:Software Engineering Institute - Carnegie Mellon University;SEI-PLS adr;dom:;;4500 5th Avenue;Pittsburgh;PA;15213 email;internet:[EMAIL PROTECTED] tel;work:+1 (412) 268 6194 tel

JESS: Rule triggers on deleted fact - additional information

? Felix Bachmann Felix Bachmann wrote: Hi, I have another problem with deleted facts. I have a rule that is activated with a fact that is already retracted from the working memory. Here the log: -- FIRE 248 SuggestModifiabilityTactics

Re: JESS: Jess 7.0RC1 require statement

Hey, Just installed the new release and found that all my (require) statements don't work anymore. The old behavior was that when using relative path names as the second parameter of required then those paths where relative to the jess file that has the required statement in it. This doesn't

JESS: Rules fireing on extended deftemplate

Hi, I have a very strange behavior with extended deftemplates. Here the definition: (defmodule Logger) (deftemplate AskQuestionLogged extends MAIN::AskQuestion (slot oldID (type OBJECT)) ) Then I have a rule that checks MAIN::AskQuestion and produces Logger::AskQuestionLogged, which looks

Re: JESS: Rules fireing on extended deftemplate

Thanks Ernest, that was new information to me. Need to think how to utilize that for my application Felix friedman_hill ernest j wrote: I think Felix Bachmann wrote: Then I have a rule that checks MAIN::AskQuestion and produces Logger::AskQuestionLogged, which looks like: (defrule

JESS: accumulate CE

Hi, I have an unfortunate, unpredictable behavior with the accumulate CE. I really like accumulate but now have to remove it from my code because every now and then it finds deleted facts. I tried to have an repeatable, simple example, but every time when I scale down, the error disappears.