interestingly, this is the premise upon which i wrote my genetic board evaluator. for what it's worth, writing good go programs using a specialized 'go instruction set' isn't any easier or more intuitive than using, say, 80386 instructions. it just makes certain operations take less 'instruction lines' of code to complete. that's all. not clock cycles. this will reduce the search space for a genetically-evolved system, which is nice, but (obviously) doesn't change the speed.
now, when my board evaluator is good enough to actually do something meaningful, i'll be happy to have someone drop it into an ASIC to see how much differently it performs. :) if you don't have the board-evaluation function written in advance, having access to specialized hardware that performs go functions faster won't make your code any better. just maybe a little bit faster. s. ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
