On Nov 13, 2007 5:01 PM, Don Dailey <[EMAIL PROTECTED]> wrote: > I must be a dinosaur - at least a minimalist - but I don't understand > the big deal about library support that has been mentioned a lot here. > My Go program doesn't use any libraries except the standard C > libraries. Since it's written in C, I have access to hundreds of > libraries for C, but I don't see any good reason to use them. >
Maybe I am too. I really only see 5 categories for libraries to use: I/O Math Timing Threading Data structures I/O is used for logging, GTP, and SGF files. Math is used by various statistics-based algorithms such as UCT D has two distinct (and incompatible) sets of standard libraries. In the default one, timing was a huge headache to get cross-platform. It mostly matched the C api. There's also a pesky interaction with the way the garbage collector interacts with sleep commands. With the (better?) one, installation of the compiler with library was a pain, and achieving line-buffered I/O was extremely non-trivial. It took multiple attempts to figure out (mostly due to poor documentation). I'd say libraries played a huge role in ramping up with a new language. Like any situation, practice with standard libraries makes them really easy to use. The problem is learning them to start with.
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
