I think Jason Morris wrote: > I have been structuring my Jess scripting code in modules, placing them in > separate files, and calling them from a master *.clp file like so.. > > ;;======= pat.clp ============ > ;; Application batch script > (clear) > (watch all) > (batch pat_main.clp) > (batch pat_ask.clp) > (batch pat_startup.clp) > (batch pat_survey.clp) > (batch pat_recommend.clp) > (batch pat_report.clp) > (batch pat_run.clp) > (start-pat)
... > > So far, it seems to work nicely, since I can comment out files that are > in-progress and isolate bugs better. > Are there any pitfalls to this approach (namely calling batch files from > batch files in Jess) and is there a better way? This is a common and recommended way to structure Jess programs; no problems here. --------------------------------------------------------- Ernest Friedman-Hill Science and Engineering PSEs Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 PO Box 969, MS 9012 [EMAIL PROTECTED] Livermore, CA 94550 http://herzberg.ca.sandia.gov -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
