Re: [computer-go] Pattern Matcher (was M.Boon-Library)

[David Weiss <dweiss51@xxxxxxxxx>]

Mark,

     This sounds like something which will be
extremely useful.  Thanks for taking the time to 
do this.

     In my opinion, the actual pattern data will be 
more valuable than the pattern matching or pattern
editing code.  I would suggest using XML as the
pattern language.  The reasons for this are as
follows:

1) The pattern data can be used from a variety of
languages, as there are standard tools for parsing and
creating XML in a variety of languages.

2) There are standard tools for transforming XML into
other languages, so individual programs can use their
own format for representing the patterns which can be
generated automatically from the XML.

3) It is difficult to devise a complete pattern
matching language in advance, so the first version can
incorporate the attributes which you are already using
such as the number of liberties, and future versions
of the language can add new attributes as necessary.

     This is stating the problem a little differently
than in your original post.  In my view, there should
be a standard pattern language.  The pattern editor
can be written once, but the pattern matcher would
need to be written in the specific language being
used by the application, at least C and Java.


		
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail 
_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/