Article View: gnu.chess
Article #394Re: gnuchess/xboard protocol
From: Ethan A Burns
Date: Thu, 01 Jun 2006 11:32
Date: Thu, 01 Jun 2006 11:32
50 lines
3716 bytes
3716 bytes
sorry to spam but I forgot the sourceforge url: https://sourceforge.net/projects/glutboard >If anyone was curious, I have finally made a sourceforge page for my project. >I am now going to take a small break from it, however, it is playable with >gnuchess. It does castling, capturing, and basic moves but not pawn promotion >, >or en passant. > >--Ethan > >>Ethan A Burns wrote: >>> >>> http://www.tim-mann.org/xboard/engine-intf.html >>> >>> Looking at this page and comparing with output from ``gnuchess --xboard'' >>> doesn't match up. >>> >>> Does anyone have input for this? Is this document out dated now? >> >>The document is current. >> >>Deviations are bugs, or in some cases just missing features. >> >>> Chess >>> Adjusting HashSize to 1024 slots >>> ... >> >>> Testing around a bit, sending and reading (reading in a seperate thread), I > >>> found that gnuchess only seems to send output to my pipe AFTER receiving a >>> move from my program. >> >>It is easier to look at the source for this, as you'll see where output >>is done to the stdout, in xboard mode, the pipe is explicitly flushed >>(the code should have been refactored to stuff this into a subroutine). >> >>It isn't flushed for the hash output, so I think this is a clear bug >>(Indeed I'll have to check if it should be output at all). >> >>I think the reason it doesn't cause any issues for most of the programs >>that work with it because of how they do the communication. Most do a >>"ping", and check for "pong", and so eat all this dross in the output >>that shouldn't be there at start-up. >> >>I will tidy this up for the next release, but suggest the "ping"/"pong" >>check is probably worth doing in general and as a workaround if you have >>to cope with earlier GNU Chess versions. >> >>Can I ask what your program does?
Technical Details
Message-ID:
<mailman.2514.1149161579.9609.info-gnu-chess@gnu.org>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news4.google.com!newsfeed.stanford.edu!shelby.stanford.edu!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Thread: 10d71d,725a2245bee255e4 X-Google-Attributes: gid10d71d,public X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!news4.google.com!newsfeed.stanford.edu!shelby.stanford.edu!not-for-mail From: Ethan A Burns <eaburns@euler.unh.edu> Newsgroups: gnu.chess Subject: Re: gnuchess/xboard protocol Date: Thu, 01 Jun 2006 07:32:42 -0400 Lines: 52 Approved: info-gnu-chess@gnu.org Message-ID: <mailman.2514.1149161579.9609.info-gnu-chess@gnu.org> NNTP-Posting-Host: lists.gnu.org X-Trace: news.Stanford.EDU 1149161580 6621 199.232.76.165 (1 Jun 2006 11:33:00 GMT) X-Complaints-To: news@news.stanford.edu To: info-gnu-chess@gnu.org Envelope-to: info-gnu-chess@gnu.org In-Reply-To: Your message of "Thu, 01 Jun 2006 07:31:24 EDT." X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (ossipee.unh.edu [132.177.137.39]); Thu, 01 Jun 2006 07:32:48 -0400 (EDT) X-cisunix-MailScanner-Information: http://pubpages.unh.edu/notes/mailfiltering.html X-cisunix-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.465, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL -0.67) X-MailScanner-From: eaburns@euler.unh.edu X-BeenThere: info-gnu-chess@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Announcements and discussions about GNU Chess <info-gnu-chess.gnu.org> List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/info-gnu-chess>, <mailto:info-gnu-chess-request@gnu.org?subject=unsubscribe> List-Archive: <http://lists.gnu.org/pipermail/info-gnu-chess> List-Post: <mailto:info-gnu-chess@gnu.org> List-Help: <mailto:info-gnu-chess-request@gnu.org?subject=help> List-Subscribe: <http://lists.gnu.org/mailman/listinfo/info-gnu-chess>, <mailto:info-gnu-chess-request@gnu.org?subject=subscribe>