On Fri, 2007-03-02 at 17:31 +0100, Łukasz Lew wrote: > I also have a strong feelings about variables. > I believe there should be standard GTP command, "var" seems to be a good name, > that would write list of variables (with types?) > var var_x would print value of var_x > var var_x value would set the value. > > What do You think?
It's a bad idea for a protocol like this in my opinon. What purpose does it serve to give variables unless you also have a protocol to agree on what the variables mean? If I send "var x = 7" what is the controller supposed to do with that? With UCI there is a provision for a program to communicate to the controller all the settable options. These do not have to be pre-defined options although many are common. Your program may have a special setting unique to it alone and you can tell the interface about it, and the end use of the program can change that parameter or option via the interface. It's really quite nice and simple. This is the closest thing I can think of to what you are talking about. There are several classes of options and you can provide ranges. The options can be boolean such as turning something on and off, values with ranges, etc. UCI is significantly more advanced compared to GTP but I'm really hesitant to change a standard, even if it's not perfect. To go forward, GTP has to be completely changed and I have mixed feelings about this. - Don > Łukasz > > On 3/2/07, Markus Enzenberger <[EMAIL PROTECTED]> wrote: > > On Thursday 01 March 2007, Phil G wrote: > > > I would like to suggest using the command "setup_sequence" instead to > > > miror > > > the "play_sequence" command which was introduced by GoGui (I believe). > > > > I finally followed the GTP (draft) standard and used a prefix separated by a > > hyphen for non-standard extension commands, so "play_sequence" > > became "gogui-play_sequence". > > > > "setup_sequence" wouldn't be a good name, because the setup stones are not a > > sequence, you can specify them in any order. > > > > There will also be a second command "gogui-setup_player" for setting the > > color > > to play, but support for that is optional, since it is not strictly > > necessary > > that the engine is informed about the color to play. The genmove and play > > commands are sent with a color argument anyway. > > If an engine does not support gogui-setup, setup stones will be sent as > > moves > > as previously. > > > > - Markus > > _______________________________________________ > > computer-go mailing list > > [email protected] > > http://www.computer-go.org/mailman/listinfo/computer-go/ > > > _______________________________________________ > computer-go mailing list > [email protected] > http://www.computer-go.org/mailman/listinfo/computer-go/ _______________________________________________ computer-go mailing list [email protected] http://www.computer-go.org/mailman/listinfo/computer-go/
