[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Programming advanced strategy



I agree very much with Mousheng Xu on this.

By the way, to add and expand a little on this, 
  a right/wise separation, interaction between, and implementation of, hard
rules and soft rules is very important in this context.
  Here hard rules are normally represented by first-degree sub-algorithms,
which could achieve optimal in principle; 
  while soft rules are stored as configurable data, always have potential to
optimize.

Of course the above does not say what is right/wise, and more explanation is
needed here.

Charles Yu

A: algorithm (hard rules)
S: data structure
R: soft rules (in the form of easy to config/adjust data)
M: modularity

-----Original Message-----
From: Xu, Mousheng [mailto:moushengxu@xxxxxxxxxxxxxxxxx]
Sent: Thursday, September 30, 1999 5:27 PM
To: computer-go@xxxxxxxxxxxxxxxxx
Subject: RE: Programming advanced strategy


I was wondering whether go concepts could be reduced to objects as in
object-oriented programming. Each object would have its place in a
hierarchy, and would have properties and methods (all of which could be
inspected, of course).

* I am sure go concepts could be mapped into almost any styles of
programming, OO or not. Mapping into OO might help clear programming a
little or a lot, and it is very creative, but it won't fundamentally
improve the strength of your program. No!!! :)

-- Mousheng Xu