[[explain int a b c
simplify int a b c
declare a as b c
+bad command
]])
AT_DATA([check.awk],
AT_CHECK([LC_ALL=C cdecl99 --file=input || exit 42], [42], [], [stderr])
AT_CHECK([$AWK -v progname="$progname" -f check.awk stderr])
+exec 3<input
+set x; shift
+while read line <&3; do
+ set x "$@" "--execute=$line"; shift;
+done
+AT_CHECK([LC_ALL=C cdecl99 "$@" || exit 42], [42], [], [stderr])
+AT_CHECK([$AWK -v progname="$progname" -f check.awk stderr])
+
AT_CLEANUP
AT_SETUP([cdecl99 invalid character error messages])
-$AWK -f- >test.dat </dev/null <<'EOF'
+$AWK -f - >test.dat <<'EOF'
BEGIN {
print "explain \1";
print "explain \377";
]])
AT_CLEANUP
+
+AT_SETUP([cdecl99 interactive mode])
+
+AT_DATA([test.dat],
+[[explain int () int
+explain int x;
+quit
+]])
+
+AT_CHECK([cdecl99 --quiet --interactive <test.dat], [0], [stdout], [ignore])
+
+# If built with readline support, then the input commands (including their
+# trailing newlines) will be captured by AT_CHECK. Otherwise, they are not:
+# the output just directly follows the prompt, and the final prompt will
+# not end with a newline. Attempt to paper over these differences.
+AT_DATA([check.sed],
+[[/> [eq]/d
+:loop
+s/^> //
+t loop
+/^$/d
+]])
+
+AT_CHECK([echo >>stdout; sed -f check.sed stdout], [0],
+[declare x as int
+])
+
+AT_CLEANUP