Author: Uri Blass
Date: 04:47:09 06/12/04
Go up one level in this thread
On June 12, 2004 at 00:20:59, Dan Honeycutt wrote:
>On June 11, 2004 at 21:05:14, Uri Blass wrote:
>
>>On June 11, 2004 at 12:33:49, Dan Honeycutt wrote:
>>
>>>On June 11, 2004 at 09:19:24, Thorsten Greiner wrote:
>>>
>>>>On June 11, 2004 at 08:30:29, Uri Blass wrote:
>>>>>
>>>>>The question is how to do it.
>>>>
>>>>I would suggest to put a version number in the source file which you increment
>>>>with each release. You can then assemble the names of the needed files like
>>>>this:
>>>>
>>>>--> snip <--
>>>>
>>>>#include <stdio.h>
>>>>
>>>>#define VERSION "237"
>>>>
>>>>#define BOOKFILE "book_" VERSION ".bin"
>>>>
>>>>int main(int argc, char *argv[]) {
>>>>
>>>> printf("I will use bookfile %s\n", BOOKFILE);
>>>>
>>>> return 0;
>>>>}
>>>
>>>I strongly agree with Thorsten. I don't keep old versions of engines. When I
>>>upgrade Movei, I copy the new version to my Movei folder and then rename the
>>>executable to Movei.exe. That way I don't have to change anything in Winboard,
>>>Arena etc. I don't think an engine should depend on it's name in order to find
>>>it's data files.
>>>
>>>Dan H.
>>
>>I think that it is better to keep old version of engines because you may want to
>>do a match between the old version and the new version to test if there is an
>>improvement.
>>
>>I also keep old source code so in case that I see no progress I can go back to
>>the old version.
>>
>
>For one's own engine I agree with you 100 percent, but for other engines - there
>are just too many of them. I can't test all of them so I assume the latest
>version of Movei is the best. On occasion I will be wrong but I count on you to
>fix that.
>
>Dan H.
The last public version is the best but I change number for new version when
I do not know if the new version is better.
Uri
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.