Author: Peter Fendrich
Date: 05:44:35 12/02/99
Go up one level in this thread
On December 02, 1999 at 08:26:02, Ulrich Tuerke wrote: >On December 02, 1999 at 08:18:19, Peter Fendrich wrote: > >>When storing all these sets of positional sac's that have been around here, I >>have a problem with the form: >>6k1/8/p3r2p/1p1pPpp1/1n1pP3/1Pq4P/PR4PB/3QN1K1 b - - id Spassky; bm d5e4; >>where the bm opcode is behind the id. >>In the EPD-string above, bm will not be recognised by EPD2Diag, but if it >>is shifted before the id opcode it works. > >If I remember correctly, the id string has to be switched between a pair of >quotation marks, i.e. id "Spassky"; bm d5e4 >if this is true, then it is a mistake in the EPD notation, not a bug in the >tool. Another mistake in the above EPD notattion is the format of the move. >According to SPEC it has to be SAN format (e.g. dxe4) > >Uli > >> >>A known bug? >> >>//Peter You're absolutely right! I checked and found: 16.2.26 Opcode "id": position identification The opcode "id" is used to provide a simple identifying label for the indicated position. It takes a single string operand. etc... In another place of this standard I found: A string is a set of contiguous printing characters delimited by a quote character at each end. You're right about the move format as well, but shame on the program that can't interpret d5e4! //Peter
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.