-
Your understanding is correct.
2009-11-10 01:00:46 UTC in CLIPS Rule Based Programming Language
-
There are different ways that you can wrap a development GUI around CLIPS, but they revolve around an internal command string maintained by CLIPS. The non-GUI command line version of CLIPS invokes the CommandLoop function which loops calling an event function that stuff characters into the command string(using ExpandCommandString). When a complete command is found, it is executed, the command...
2009-11-09 00:44:50 UTC in CLIPS Rule Based Programming Language
-
garyriley committed revision 77 to the CLIPS Rule Based Programming Language SVN repository, changing 1 files.
2009-11-05 17:15:08 UTC in CLIPS Rule Based Programming Language
-
garyriley committed revision 76 to the CLIPS Rule Based Programming Language SVN repository, changing 3 files.
2009-11-05 17:12:57 UTC in CLIPS Rule Based Programming Language
-
My mistake. I forgot that the fact identifier is printed at the beginning of the string. There should always be a space between the fact-identifier and the fact so one way to fix this issue is to use a loop to clean up the string and place spaces until you encounter the first space. Alternately, you could use the GetFactPPForm function as the basis of a new function that returns just the fact...
2009-10-11 15:15:57 UTC in CLIPS Rule Based Programming Language
-
It's a little more complicate because you can't directly use the internal data structures from one environment (facts in this case) and pass them to the other. You need to make a copy of the fact and pass it into the other environment. That basically means creating the fact and then copying over the slots one by one. Alternately if you know your facts are of fixed length (i.e. you don't have...
2009-10-06 14:24:16 UTC in CLIPS Rule Based Programming Language
-
There's a discussion of modules in the Basic Programming Guide. If you don't know what they are, then you're probably not using them, so you can just pass in NULL for that argument.
2009-10-04 16:22:11 UTC in CLIPS Rule Based Programming Language
-
Yes, there are plenty of functions in the API that you could use. What you'd do is highly specific on your needs. A generalized solution is much more difficult to implement than one to handle a specific situation.
2009-10-01 02:46:15 UTC in CLIPS Rule Based Programming Language
-
No, there's not a generalized mechanism that allows you to do this (such as a clone environment API call). Very crudely, you could save all of the constructs to a file and all of the facts to a file using the Save and SaveFacts API calls and then reload them into the target environment, but there are numerous limitations to this approach.
2009-09-30 01:13:45 UTC in CLIPS Rule Based Programming Language
-
Assertions from external sources have to occur between rule firings. So if you have CLIPS embedded, you could fire one rule at a time and after each firing, have your sensors assert any new facts. Alternately you could use the AddRunFunction API call to register a function that's called after each rule execution and just let CLIPS run. Either of these approaches would require polling the...
2009-09-05 21:19:18 UTC in CLIPS Rule Based Programming Language
