Re: OpenGo Suggestion as Re: Eureka

[David Mechner <mechner@xxxxxxxxxxxxxxxxx>]

The thing is that the input of the function is /not/ the board
configuration; it's the higher-level knowledge - blocks and groups and
patterns. My eye routines have to know what a group is and how to access
groups and traverse each of the blocks that make up the group and
(maybe) each of the points that make each the block, and then how to get
at all the eye patterns (or, in our case, "assertions" about where eye
patterns have matched) that relate to the group in question.  See - not
modular.

-David

>     I'd say your "eye" is a good example. People can surely make use
> of it.  Suppose the input of your function is the board
> configuration, the output is an eye structure/class. You just let
> people know what the inputs & outputs are, the return values and
> potential side-effects. It's up to the others to decide if they can
> make use of it. Even your representation of the board configuration,
> the structure describing an eye can be different from those of the
> others, one can convert his board representation to yours, and add
> your eye structure to his program. If your source code is available,
> people can discuss it, make suggestions, or modify it to make it
> "better" in some sense. Also, we may standardize things like the
> representation of a board configuration, an eye class ...

-- 
David A. Mechner            Center for Neural Science
mechner@xxxxxxxxxxxxxxxxx         4 Washington Place, New York, NY 10003
212.998.3580                http://cns.nyu.edu/~mechner/