# Expected results for tests/fixtures/*.pas  -  one line per fixture:
#
#   <fixture-basename>	OK	<code>	<data>
#   <fixture-basename>	ERR	<tp3-error-no>	<relative-pos>
#
# Both the verdict AND the numbers are asserted by run_compile_tests.sh, so a
# regression in the *reported error position* fails the suite just like a
# regression in the generated code.  That matters: error positions were once
# silently wrong (a multi-character string literal swallowed the rest of the
# source, so every later error pointed at end-of-file), and nothing caught it
# because the old harness only printed the position for a human to squint at.
#
# Re-baseline deliberately, never to make a red test go green: if a fixture's
# expectation has to change because the compiler legitimately improved, change
# it in the same commit as the fix and say why in the message.
#
# ERR 102 = ENoLib, the original's "not implemented" path.  The five ERR rows
# below are all unimplemented features, not parser bugs:
#   t02 t03 t05 t17  multi-character string literal (string runtime pending)
#   t14               'array [..] of <type>' at its point of use
#   uierror           deliberate syntax error, pinned by the editor UI test

t01_minimal	OK	26	260
t02_writeln	ERR	102	33
t03_inline_comment	ERR	102	41
t04_var	OK	45	262
t05_own_line_comment	ERR	102	65
t06_two_args	OK	49	260
t07_big	OK	99	262
t08_const	OK	32	262
t09_if	OK	64	262
t10_while	OK	72	262
t11_for	OK	66	262
t12_repeat	OK	69	262
t13_proc	OK	50	262
t14_types	ERR	102	83
t15_label	OK	35	262
t16_str1	OK	39	260
t17_two_str	ERR	102	34
t18_writeln_bare	OK	29	260
t19_int1	OK	39	260
t20_str3	OK	59	260
t21_mixed	OK	59	260
t22_case	OK	93	262
uierror	ERR	41	331