[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
doc: clarify the glossary item about kinds
From: |
Akim Demaille |
Subject: |
doc: clarify the glossary item about kinds |
Date: |
Thu, 7 May 2020 08:39:28 +0200 |
commit 11727aa71977c95730ea9353ca21076b4d97787a
Author: Akim Demaille <address@hidden>
Date: Thu May 7 08:34:45 2020 +0200
doc: clarify the glossary item about kinds
* doc/bison.texi (Glossary): here.
diff --git a/doc/bison.texi b/doc/bison.texi
index 4bb3e97b..36f95258 100644
--- a/doc/bison.texi
+++ b/doc/bison.texi
@@ -14942,12 +14942,21 @@ A continuous flow of data between devices or programs.
@item Kind
``Token'' and ``symbol'' are each overloaded to mean either a grammar symbol
(kind) or all parse info (kind, value, location) associated with occurrences
-of that grammar symbol from the input. To disambiguate, we use ``token
-kind'' and ``symbol kind'' to mean both grammar symbols and the types that
-represent them in a base programming language (C, C++, etc.). However, we
-use ``token'' and ``symbol'' without the word ``kind'' to mean parsed
+of that grammar symbol from the input. To disambiguate,
+
+@itemize
+@item
+we use ``token kind'' and ``symbol kind'' to mean both grammar symbols and
+the values that represent them in a base programming language (C, C++,
+etc.). The names of the types of these values are typically
+@code{token_kind_t}, or @code{token_kind_type}, or @code{TokenKind},
+depending on the programming language.
+
+@item
+we use ``token'' and ``symbol'' without the word ``kind'' to mean parsed
occurrences, and we append the word ``type'' to refer to the types that
represent them in a base programming language.
+@end itemize
In summary: When you see ``kind'', interpret ``symbol'' or ``token'' to mean
a @emph{grammar symbol}. When you don't see ``kind'' (including when you
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- doc: clarify the glossary item about kinds,
Akim Demaille <=