Hi All, One of my Outlook rules my have zapped someone's reply, so please forgive me for asking my question again - albeit a shorter version this time:
On pg. 169 of JIA, Ernest makes the comment "...You should be thinking about putting together a complete test harness now..", so 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) Q. Though it seems to run fine now, I'm wondering if there are any pitfalls to calling batch files from batch files in Jess like this; and, is there a better/preferred/best-practice way to automate this kind of code/run/debug cycle? Thanks! -JM --- Jason Morris Morris Technical Solutions [EMAIL PROTECTED] www.morristechnicalsolutions.com fax/phone: 503.692.1088 -------------------------------------------------------------------- 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] --------------------------------------------------------------------
