aboutsummaryrefslogtreecommitdiff
path: root/gdb/expread.y
diff options
context:
space:
mode:
authorJohn Gilmore <gnu@cygnus>1991-04-05 09:02:10 +0000
committerJohn Gilmore <gnu@cygnus>1991-04-05 09:02:10 +0000
commit3f2e006b77f217bbf4a4cb9299cf248058a44ed3 (patch)
tree60b9a78e945e02698d856ea5b82982fe549b26f2 /gdb/expread.y
parent07d021a6ae8d3ed9da9f55c8623739e7a716308e (diff)
downloadgdb-3f2e006b77f217bbf4a4cb9299cf248058a44ed3.zip
gdb-3f2e006b77f217bbf4a4cb9299cf248058a44ed3.tar.gz
gdb-3f2e006b77f217bbf4a4cb9299cf248058a44ed3.tar.bz2
*** empty log message ***
Diffstat (limited to 'gdb/expread.y')
-rwxr-xr-xgdb/expread.y10
1 files changed, 8 insertions, 2 deletions
diff --git a/gdb/expread.y b/gdb/expread.y
index 3b19750..acced91 100755
--- a/gdb/expread.y
+++ b/gdb/expread.y
@@ -857,8 +857,14 @@ name : NAME { $$ = $1.stoken; }
name_not_typename : NAME
| BLOCKNAME
- | NAME_OR_INT
- | NAME_OR_UINT
+/* These would be useful if name_not_typename was useful, but it is just
+ a fake for "variable", so these cause reduce/reduce conflicts because
+ the parser can't tell whether NAME_OR_INT is a name_not_typename (=variable,
+ =exp) or just an exp. If name_not_typename was ever used in an lvalue
+ context where only a name could occur, this might be useful.
+ | NAME_OR_INT
+ | NAME_OR_UINT
+ */
;
%%