🚀 go-pugleaf

A number of people have reported this bug.  Mike McGann was kind
enough to send me the fix below.  Mike will be including this fix when
he releases patchlevel 62.

I believe the problems caused by this bug are intermittent, and some
users do not see them at all, because the effect of the bug is to
access two arrays out of bounds (starting at element -1 instead of 0).
Thus the results depend on what variable the compiler assigns to the
memory locations just before the start of the arrays.

	--Tim


Return-Path: mwm@hasler.ascom.ch
Received: by src-mail.pa.dec.com; id AA10763; Mon, 1 Mar 93 00:35:39 -0800
Received: by inet-gw-2.pa.dec.com; id AA03579; Mon, 1 Mar 93 00:35:35 -0800
Received: by hslrswi.hasler.ascom.ch (5.65c/6.32)
	id AA09974; Mon, 1 Mar 1993 09:33:00 +0100 
Date: Mon, 1 Mar 1993 09:33:00 +0100
From: Mike McGann  <mwm@hasler.ascom.ch>
Message-Id: <199303010833.AA09974@hslrswi.hasler.ascom.ch>
To: mann
Subject: p61


the fix for the castle illegal move problem is in
init.c about line 299 it has:

compptr = oppptr = -1;

it should be:

compptr = oppptr = 0;

mike