* tests/calc.at (AT_CHECK_CALC): Adjust: there are now additional

[bison.git] / TODO

diff --git a/TODO b/TODO
index bc474d21aee7183e7eeada910dd8e17485e51910..89c5a07075e17fa18f7c0eb8605a93df28fcd3b7 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,5 +1,20 @@
 -*- outline -*-
 
+* documentation
+Explain $axiom (and maybe change its name: BTYacc names it goal).
+Complete the glossary (item, axiom, ?).
+
+* report documentation
+Extend with error.  The hard part will probably be finding the right
+rule so that a single state does not exhibit to many yet undocumented
+``features''.  Maybe an empty action ought to be presented too.  Shall
+we try to make a single grammar with all these features, or should we
+have several very small grammars?
+
+* documentation
+Some history of Bison and some bibliography would be most welcome.
+Are there any Texinfo standards for bibliography?
+
 * Several %unions
 I think this is a pleasant (but useless currently) feature, but in the
 future, I want a means to %include other bits of grammars, and _then_
@@ -21,6 +36,26 @@ When implementing multiple-%union support, bare the following in mind:
          char *sval;
        }
 
+* --report=conflict-path
+Provide better assistance for understanding the conflicts by providing
+a sample text exhibiting the (LALR) ambiguity.
+
+* report
+Solved conflicts should not be reported in the beginning of the file.
+Rather they should be reported within each state description.  Also,
+now that the symbol providing the precedence of a rule is kept, it is
+possible to explain why a conflict was solved this way.  E.g., instead
+of
+
+   Conflict in state 8 between rule 2 and token '+' resolved as reduce.
+
+we can (in state 8) report something like
+
+   Conflict between rule 2 and token '+' resolved as reduce
+   because '*' < '+'.
+
+or something like that.
+
 * Coding system independence
 Paul notes: