3 |
* URGENT: Documenting C++ output |
* URGENT: Documenting C++ output |
4 |
Write a first documentation for C++ output. |
Write a first documentation for C++ output. |
5 |
|
|
6 |
|
* Report and GLR |
7 |
|
How would Paul like to display the conflicted actions? In particular, |
8 |
|
what when two reductions are possible on a given lookahead, but one is |
9 |
|
part of $default. Should we make the two reductions explicit, or just |
10 |
|
keep $default? See the following point. |
11 |
|
|
12 |
|
* Report and Disabled Reductions |
13 |
|
See `tests/conflicts.at (Defaulted Conflicted Reduction)', and decide |
14 |
|
what we want to do. |
15 |
|
|
16 |
* value_components_used |
* value_components_used |
17 |
Was defined but not used: where was it coming from? It can't be to |
Was defined but not used: where was it coming from? It can't be to |
18 |
check if %union is used, since the user is free to $<foo>n on her |
check if %union is used, since the user is free to $<foo>n on her |
26 |
* documentation |
* documentation |
27 |
Explain $axiom (and maybe change its name: BTYacc names it `goal', |
Explain $axiom (and maybe change its name: BTYacc names it `goal', |
28 |
byacc `$accept' probably based on AT&T Yacc, Meta `Start'...). |
byacc `$accept' probably based on AT&T Yacc, Meta `Start'...). |
29 |
Complete the glossary (item, axiom, ?). |
Complete the glossary (item, axiom, ?). Should we also rename `$'? |
30 |
|
BYacc uses `$end'. `$eof' is attracting, but after all we may be |
31 |
|
parsing a string, a stream etc. |
32 |
|
|
33 |
* Error messages |
* Error messages |
34 |
Some are really funky. For instance |
Some are really funky. For instance |
38 |
is really weird. Revisit them all. |
is really weird. Revisit them all. |
39 |
|
|
40 |
* Report documentation |
* Report documentation |
41 |
Extend with error. The hard part will probably be finding the right |
Extend with error productions. The hard part will probably be finding |
42 |
rule so that a single state does not exhibit to many yet undocumented |
the right rule so that a single state does not exhibit too many yet |
43 |
``features''. Maybe an empty action ought to be presented too. Shall |
undocumented ``features''. Maybe an empty action ought to be |
44 |
we try to make a single grammar with all these features, or should we |
presented too. Shall we try to make a single grammar with all these |
45 |
have several very small grammars? |
features, or should we have several very small grammars? |
46 |
|
|
47 |
* Documentation |
* Documentation |
48 |
Some history of Bison and some bibliography would be most welcome. |
Some history of Bison and some bibliography would be most welcome. |