Lines Matching refs:record

183 record markers, start-of-line byte counts, fixed length records, and so forth.
277 markers for secondary record structure imposed by specific operating systems.
1626 annotate each EPD record with a numeric score, and then having BOOKUP import
1985 A single FEN record uses one text line of variable length composed of six data
2247 Any given opcode appears at most once per EPD record.  Multiple operations in a
2248 single EPD record should appear in ASCII order of their opcode names
2351 2) As the EPD record for each position in the game is processed, the comment
2353 EPD record are interpreted from left to right.)  Because operations appear in
2425 record.  The draw_claim opcode takes no operands.
2432 appear as part of the same EPD record; this move is considered played from the
2527 same EPD record, the first move of the predicted variation is the same as the
2540 If a "pm" (predicted move) operation is also present in the same EPD record,
2584 receiver of the EPD record.  The second operand is the name of the player
2585 (program or human) at the address who is the actual receiver of the EPD record.
2593 sender of the EPD record.  The second operand is the name of the player
2594 (program or human) at the address who is the actual sender of the EPD record.
2613 2) As the EPD record for each position in the game is processed, the variation
2615 in n EPD record are interpreted from left to right.)  Because operations appear
2721 PGC data is composed of a sequence of PGC records.  Each record is composed of
2722 a sequence of one or more bytes.  The first byte is the PGN record marker and
2723 it specifies the interpretation of the remaining portion of the record.  This
2724 remaining portion is composed of zero or more PGN record items.  Item types
2801 moves, and no annotations or comments.  This record type is used as an
2802 alternative to the general game data begin/end record pairs described below.
2806 record.  In order, these are:
2828 follow marker 0x02 to form the "tag pair" record; in order these are:
2838 follows marker 0x03 to form the "short move sequence" record; this is:
2846 follows marker 0x04 to form the "long move sequence" record; this is:
2854 associated items; it is a complete record by itself.  Instead, it marks the
2856 corresponding "general game data end" record are considered to be part of the
2857 same game.  (PGC record type 0x01, "reduced export format single game", is not
2858 permitted to appear within a general game begin/end record pair.  The general
2859 game construct is to be used as an alternative to record type 0x01 in those
2866 associated items; it is a complete record by itself.  Instead, it marks the end
2868 (and earlier appearing) "general game data begin" record are considered to be
2877 form the "simple-nag" record; this is:
2885 Variation).  It has no associated items; it is a complete record by itself.
2887 annotation.  It is considered an opening bracket for a later rav-end record;
2895 Variation).  It has no associated items; it is a complete record by itself.
2898 record; the recursive annotation is completely described between the bracket
2909 record is limited to use for non-archival data.  There is one item that follows
2910 marker 0x0a to form the "escape-string" record; this is the string data being