this code (and the related create) is unusual: (defn reset [] "Reset: clear and initialize all memories" (def =AMEM= (object-array @ACNT)) (def =BMEM= (object-array =BCNT=)) (def =FMEM= (create-fmem =TEMPL=)) (def =FMMB= (create-fmem =TEMPL=)) (def =FIDS= (HashMap.)) (def CFSET (atom nil)) (def FCNT (atom 0)))
It implies that you can only have one set of rules/engine in any usage of the library. Even if you plan to use mutable data - this seems to create additional restrictions. Why not put all of these into a map and pass that around as the ruleset/engine state? On Tuesday, 13 May 2014 23:32:49 UTC+10, ru wrote: > > Alan. You absolutely right! Clojure must return thinking of programmers > back to solving problems from vanity and narcissism of unnecessary > complexity :) I certainly will look on Clara more attentively and may be > switch to it in my applications. > > cheers, > Ru > > понедельник, 12 мая 2014 г., 17:47:44 UTC+4 пользователь ru написал: >> >> New feature: added Java interface. Eclipse project example. >> >> Home: https://github.com/rururu/rete4frames >> >> Have fun! >> >> Sincerely, >> Ru >> > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
