1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00

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 012abebab1, 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.
This commit is contained in:
Tom Lane
2014-05-28 15:41:55 -04:00
parent 433cacfc0f
commit ece7aa8b0f
8 changed files with 8 additions and 8 deletions

View File

@ -93,7 +93,7 @@ static int num_columns_read = 0;
%}
%expect 0
%name-prefix="boot_yy"
%name-prefix "boot_yy"
%union
{

View File

@ -166,7 +166,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}

View File

@ -51,7 +51,7 @@ Node *replication_parse_result;
%}
%expect 0
%name-prefix="replication_yy"
%name-prefix "replication_yy"
%union {
char *str;

View File

@ -557,7 +557,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 {

View File

@ -110,7 +110,7 @@ static List *read_raise_options(void);
%}
%expect 0
%name-prefix="plpgsql_yy"
%name-prefix "plpgsql_yy"
%locations
%union {

View File

@ -20,7 +20,7 @@ TestSpec parseresult; /* result of parsing is left here */
%}
%expect 0
%name-prefix="spec_yy"
%name-prefix "spec_yy"
%union
{