Author: leonid
Date: 14:35:29 11/10/99
Go up one level in this thread
On November 10, 1999 at 13:49:49, blass uri wrote: >On November 10, 1999 at 07:15:37, leonid wrote: > >> >>>You can do something faster in assembly, but it takes such a long time to >>>develop it that in the end you lose your advantage. >>> >>>Because chess programming is about being creative, and assembly lengthens the >>>time between the idea and the implementation. That's the key. >>> >>> >>> Christophe >> >>In reality, it is not writing the code that is the most time consuming in >>programming (at least in mine) but verification of each version of logic. >>Verification for speed. Writing the code take hardly 5 or 10% from the total >>time for creating the game. > >How much time do you use for fixing bugs? > >I did not write chess programs but my small experience with C shows that I use a >lot of time for fixing logic bugs when the program does not do what it is >supposed to do. > >It can be something stupid(for example if I write ; that I should not write and >do not pay attention to it) and it can take an hour to discover where is the >problem when you have a project of some hundreds lines. > >Uri It take a lot of time to fix the bugs, like you do, but once again it is only fraction of time compared with the time consumed by speeding the game. I will say that if the time for writing the game as such take 5%, fixing the bugs take around 16% and the rest for finding what version of logic provide higher speed. Leonid.
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.