db_yyerror should be compiled only if YYDEBUG is nonzero

Thread View: gnu.g++.bug

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Paul Eggert Tue, 14 Nov 1989 02:23

#578

Author: Paul Eggert
Date: Tue, 14 Nov 1989 02:23

27 lines
1044 bytes

Some versions of bison generate yytname[] only if YYDEBUG is nonzero.
But db_yyerror() in cplus-parse.y always references yytname[].
db_yyerror() is needed only in debugging situations,
so it might as well depend on YYDEBUG too.  Here is a fix.

*** old/cplus-parse.y	Mon Nov 13 18:16:14 1989
--- new/cplus-parse.y	Mon Nov 13 16:10:10 1989
***************
*** 2991,2996 ****
--- 2991,2997 ----
  
  %%
  
+ #if YYDEBUG != 0
  db_yyerror (s, yyps, yychar)
       char *s;
       short *yyps;
***************
*** 3028,3033 ****
--- 3029,3035 ----
      }
  #endif
  }
+ #endif
  
  void
  yyerror (string)

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads