Re: OpenGo / GNU / GPL Name Confusion

[Fuming Wang <fuming@xxxxxxxxxxxxxxxxxxxxxxxxx>]

<Pine.SGI.3.96.981014075027.13795A-100000@xxxxxxxxxxxxxxxxx>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Sequence: 480
Precedence: list



On Mon, 12 Oct 1998, Jeffrey Greenberg wrote:

> Fuming,
>     I will have this licensing issue resolved enough to release the code by the
>     weekend.  Have you already released jago/gnu-go?  Can you wait till I
>     finish my move?  8-)
> 
>     On a technical level,  please consider the following:
> 
>     Currently the OpenGo interface is a C++ compile time interface.  So there
> are two
>     choices in the short term:
>     A. make a version of OpenGo which is based on Java
>     B. make a version of OpenGo that is compiler/os independent.
> 
>     Choice A seems like a good way to maintain two separate bodies of code:
>         I'm against it.
>     Choice B would be a better way: less code to maintain plus other benefits.
>         I'm thinking along the lines of an IPC abstraction that would hide the
>         actual mechanism which might be messages or pipes or shared memory.
>         It would require two changes:
>             1. creating the "java-side" (or whatever language side)
>                 ipc mechanism to connect to the engine.
>             2. creating an OpenGo player-proxy (C++) that does the ipc out to
>                 the engine app.
> 

Hi Jeffrey,

I was thinking inline of Choice B too, i.e. use the same hooks (API)
between GUI and engine. However, the this will probably happen only after
OpenGo becomes mature. So, go ahead release your
code. Thanks for doing a great favor to the computer Go.

Cheers,

Fuming Wang