Yes, that sounds reasonable to me. Really, the only difference in required and recommended is whether the end user sends back "not_implemented" or implements them. So we would provide a complete set, and then specify which ones absolutely must function to not break interfaces.
Don
From: leary@nwlink.com
On Wed, Aug 08, 2001 at 11:58:10PM -0400, Don Dailey wrote:
P.S. So maybe we should call this the "recommend" gtp command set, and let programmers decide what to implement? Then we don't have to argue about whether "undo" is a useful feature or not.
my $.015:
maybe a multi-tier approach:
perhaps have the minimal core be "required", maybe another set of commands be "recommended" and/or "optional" for the mostly solid stuff. And perhaps "development" or "alpha" for the totally changeable stuff.
-- _______________________________________________ gtp mailing list gtp@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/gtp