X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/149365be0121937061a88af843e100828f605fa8..dda7a53e4d98add4c5ab9ba2cbc6a2bbf40e896c:/tests/input.at

diff --git a/tests/input.at b/tests/input.at
index f397811c..78308d0c 100644
--- a/tests/input.at
+++ b/tests/input.at
@@ -92,23 +92,38 @@ AT_CLEANUP
 
 AT_SETUP([Torturing the Scanner])
 
-AT_DATA([input.y],
+AT_DATA_GRAMMAR([input.y],
 [[%{
 /* This is seen in GCC: a %{ and %} in middle of a comment. */
 const char *foo = "So %{ and %} can be here too.";
 
-#ifdef __STDC__
+#if 0
+/* These examples test Bison while not stressing C compilers too much.
+   Many C compilers mishandle backslash-newlines, so this part of the
+   test is inside "#if 0".  The comment and string are written so that
+   the "#endif" will be seen regardless of the C compiler bugs that we
+   know about, namely:
+
+     HP C (as of late 2002) mishandles *\[newline]\[newline]/ within a
+     comment.
+
+     The Apple Darwin compiler (as of late 2002) mishandles
+     \\[newline]' within a character constant.
+
+   */
+
 /\
-* A comment with backslash-newlines in it. %{ %} *\
+* A comment with backslash-newlines in it. %} *\
+\
 /
+/* { Close the above comment, if the C compiler mishandled it.  */
 
 char str[] = "\\
 " A string with backslash-newlines in it %{ %} \\
+\
 "";
 
-char apostrophe = '\\
-'\
-';
+char apostrophe = '\'';
 #endif
 
 #include <stdio.h>
@@ -188,6 +203,8 @@ yyerror (const char *msg)
 }
 ]])
 
+# Pacify Emacs'font-lock-mode: "
+
 AT_DATA([main.c],
 [[typedef int value_t;
 #include "input.h"
@@ -202,7 +219,9 @@ main (void)
 ]])
 
 AT_CHECK([bison -d -v -o input.c input.y])
-AT_COMPILE([input], [input.c main.c])
+AT_COMPILE([input.o], [-c input.c])
+AT_COMPILE([main.o], [-c main.c])
+AT_COMPILE([input], [input.o main.o])
 AT_PARSER_CHECK([./input], 0,
 [[[@<:@],
 ]])