4 |
Write a first documentation for C++ output. |
Write a first documentation for C++ output. |
5 |
|
|
6 |
|
|
7 |
|
* Documentation |
8 |
|
Before releasing, make sure the documentation refers to the current |
9 |
|
`output' format. |
10 |
|
|
11 |
|
|
12 |
* Error messages |
* Error messages |
13 |
Some are really funky. For instance |
Some are really funky. For instance |
14 |
|
|
126 |
|
|
127 |
* Documentation |
* Documentation |
128 |
|
|
|
** Vocabulary |
|
|
Explain $axiom (and maybe change its name: BTYacc names it `goal', |
|
|
byacc `$accept' probably based on AT&T Yacc, Meta `Start'...). |
|
|
Complete the glossary (item, axiom, ?). Should we also rename `$'? |
|
|
BYacc uses `$end'. `$eof' is attracting, but after all we may be |
|
|
parsing a string, a stream etc. |
|
|
|
|
129 |
** History/Bibliography |
** History/Bibliography |
130 |
Some history of Bison and some bibliography would be most welcome. |
Some history of Bison and some bibliography would be most welcome. |
131 |
Are there any Texinfo standards for bibliography? |
Are there any Texinfo standards for bibliography? |