On Mon, Dec 6, 2010 at 5:18 AM, zmyrgel <timo.my...@gmail.com> wrote: > Then you didn't look close enough of my first message :) > Granted, I omitted large parts of the code in it but it showed my > evaluate function with pruning attached.
Er, I saw min calling max and max calling min, without either doing anything to prune branches or otherwise skip stuff. > Here's my evaluate function, with debugging code cleaned: [snip] > Though I'm still having some issues with my minmax. > When I'm trying to evaluate single state it returns a nil in about 1 > msec. > Seems that there are some issues with laziness as the algorithm seemed > to work somehow when I printed the debug information. You may need to wrap a doall around something, though it shouldn't make a difference unless you're using binding or mutable state or I/O somewhere. -- 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
