Author: Dann Corbit
Date: 16:49:22 06/04/99
Go up one level in this thread
On June 04, 1999 at 19:39:36, Mike Leahy wrote: >On May 27, 1999 at 20:48:55, Dann Corbit wrote: > >>From the PGN Standard > > >>16.1.4: Examples >> >>Here's the FEN for the starting position: >> >>rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1 >> >>And after the move 1. e4: >> >>rnbqkbnr/pppppppp/8/8/4P3/8/PPPP1PPP/RNBQKBNR b KQkq e3 0 1 > >This is problematic. The position is identical to... > > rnbqkbnr/pppppppp/8/8/4P3/8/PPPP1PPP/RNBQKBNR b KQkq - 0 1 > >...because the en passant capture is not legal. Purely >positional programs like Bookup are fussy about this. >Bookup considers the record with 'e3' as illegal. Programs >like Rebel solve the program by ignoring the en passant flag(!). That's a good point. I think there is a reason to have them, and a reason to ignore them. What I mean by that is that a "generator" for a program does not know, a-priori, if it will be needed or not until it examines the board. It may be faster to spew them all out and deal with it later. However, it causes much more analysis for C.A.P. than needed. There are other reasons it is simply not a good idea. So I propose a "storage" EPD format which must determine if the e.p. square has some effect. If it does not, then it must be stored to the database with the flag blank. I would also like to see semicolons in EPD between every field+operand, since this would make parsing easier.
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.