Author: Daniel Clausen
Date: 10:30:01 05/13/02
Go up one level in this thread
Hi Miguel! (and others :) On May 13, 2002 at 13:09:06, Miguel A. Ballicora wrote: >The program with the other approach won't either because It could return >eval() at ply 60th as a defensive method of programming (ugly huh? :-)). Very elegant indeed. :p And not error-prone at all, because how could I ever forget to do that. :) >In big machines like today it might not be a problem, I agree, but it >certainly is less of a problem with the global approach. Point taken, although to be sure that you never have a stack problem, you almost have to implement the whole stack by yourself. I simply have a 'limit coredumpsize 2M' in my startup-script. ;) >In fact, if you decide to move >the program one day to a different small machine (palm etc.) it may crash >because the stack is smaller. The global procedure is more portable in that >respect. You just reduce the size of the array or structure and that's it. And don't forget to change the line "if(ply==60) return eval();" accordingly. *smiles* Sargon
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.