I see the idea. Gather stats for the best go playing programs, put the
figures into CLOP. Hey presto! You now know exactly how many lines of
code the perfect Go playing program needs.
Seriously, when comparing source code sizes for different
implementations of the same thing, it's often helps if you strip out
comments and then compress the code. This removes size differences
caused by style issues such as comments, indentation and identifier
length etc. Of course comparing size of binaries also gets round these
problems, but you can run into difficulties with libraries.
Raffles
On 09/01/2012 02:51, terry mcintyre wrote:
Go programs can have databases too. They can be a compact
representation of information which might otherwise be a large amount
of case-specific code.
Terry McIntyre <[email protected]>
Unix/Linux Systems Administration
Taking time to do it right saves having to do it twice.
------------------------------------------------------------------------
*From:* Michael Williams <[email protected]>
*To:* [email protected]
*Sent:* Sunday, January 8, 2012 3:13 PM
*Subject:* [Computer-go] Lines of code
Has there been any studies into the number of lines of code in the
top chess/go programs over time? Another measure would be bytes
of executable or bytes of executable+data. Obviously the latter
grows in chess with endgame databases, so maybe that's less
interesting.
_______________________________________________
Computer-go mailing list
[email protected] <mailto:[email protected]>
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
_______________________________________________
Computer-go mailing list
[email protected]
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
_______________________________________________
Computer-go mailing list
[email protected]
http://dvandva.org/cgi-bin/mailman/listinfo/computer-go
