Commit 45b7abe5 authored by Tom Lane's avatar Tom Lane

Fix bogus %name-prefix option syntax in all our Bison files.

%name-prefix doesn't use an "=" sign according to the Bison docs, but it
silently accepted one anyway, until Bison 3.0.  This was originally a
typo of mine in commit 012abeba, and we
seem to have slavishly copied the error into all the other grammar files.

Per report from Vik Fearing; analysis by Peter Eisentraut.

Back-patch to all active branches, since somebody might try to build
a back branch with up-to-date tools.
parent c0f27628
......@@ -39,7 +39,7 @@ static NDBOX * write_point_as_box(char *s, int dim);
/* BISON Declarations */
%parse-param {NDBOX **result}
%expect 0
%name-prefix="cube_yy"
%name-prefix "cube_yy"
%token CUBEFLOAT O_PAREN C_PAREN O_BRACKET C_BRACKET COMMA
%start box
......
......@@ -42,7 +42,7 @@ static char strbuf[25] = {
/* BISON Declarations */
%parse-param {SEG *result}
%expect 0
%name-prefix="seg_yy"
%name-prefix "seg_yy"
%union {
struct BND {
......
......@@ -93,7 +93,7 @@ static int num_columns_read = 0;
%}
%expect 0
%name-prefix="boot_yy"
%name-prefix "boot_yy"
%union
{
......
......@@ -169,7 +169,7 @@ static Node *makeRecursiveViewSelect(char *relname, List *aliases, Node *query);
%pure-parser
%expect 0
%name-prefix="base_yy"
%name-prefix "base_yy"
%locations
%parse-param {core_yyscan_t yyscanner}
......
......@@ -40,7 +40,7 @@ Node *replication_parse_result;
%}
%expect 0
%name-prefix="replication_yy"
%name-prefix "replication_yy"
%union {
char *str;
......
......@@ -572,7 +572,7 @@ add_typedef(char *name, char *dimension, char *length, enum ECPGttype type_enum,
%}
%expect 0
%name-prefix="base_yy"
%name-prefix "base_yy"
%locations
%union {
......
......@@ -110,7 +110,7 @@ static List *read_raise_options(void);
%}
%expect 0
%name-prefix="plpgsql_yy"
%name-prefix "plpgsql_yy"
%locations
%union {
......
......@@ -20,7 +20,7 @@ TestSpec parseresult; /* result of parsing is left here */
%}
%expect 0
%name-prefix="spec_yy"
%name-prefix "spec_yy"
%union
{
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment