Future/bison
1
0
Fork 0
mirror of https://git.savannah.gnu.org/git/bison.git synced 2026-03-21 18:23:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add "Java, Fortran, etc." Mention the already-existing hack that supports Bison for Java.

Browse Source 
Fix some misspellings.
This commit is contained in:
Paul Eggert
2002-08-30 11:27:05 +00:00
parent 8442d6ba22
commit 948be909e9
1 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
TODO
View File

@@ -53,7 +53,7 @@ a sample text exhibiting the (LALR) ambiguity. See the paper from
DeRemer and Penello: they already provide the algorithm. DeRemer and Penello: they already provide the algorithm.
* Extentions * Extensions
** yyerror, yysymprint interface ** yyerror, yysymprint interface
It should be improved, in particular when using Bison features such as It should be improved, in particular when using Bison features such as
@@ -108,6 +108,14 @@ Are there any Texinfo standards for bibliography?
* Java, Fortran, etc.
Add support for languages other than C and C++. Here is a proposed
patch for Java:
<http://www.goice.co.jp/member/mo/hack-progs/bison-java.html>
* Coding system independence * Coding system independence
Paul notes: Paul notes:
@@ -133,7 +141,7 @@ Show reductions. []
** %pure-parser [] ** %pure-parser []
** %token-table [] ** %token-table []
** Options which could use parse_dquoted_param (). ** Options which could use parse_dquoted_param ().
Maybe transfered in lex.c. Maybe transferred in lex.c.
*** %skeleton [ok] *** %skeleton [ok]
*** %output [] *** %output []
*** %file-prefix [] *** %file-prefix []
@@ -150,7 +158,7 @@ Find the best graph parameters. []
* doc/bison.texinfo * doc/bison.texinfo
** Update ** Update
informations about ERROR_VERBOSE. [] informations about ERROR_VERBOSE. []
** Add explainations about ** Add explanations about
skeleton muscles. [] skeleton muscles. []
%skeleton. [] %skeleton. []
@@ -171,7 +179,7 @@ First, analyze the differences between byacc and btyacc (I'm referring
to the executables). Find where the conflicts are preserved. to the executables). Find where the conflicts are preserved.
** Compare with the GLR tables ** Compare with the GLR tables
See how isomorphic the way BTYacc and the way the GLR adjustements in See how isomorphic the way BTYacc and the way the GLR adjustments in
Bison are compatible. *As much as possible* one should try to use the Bison are compatible. *As much as possible* one should try to use the
same implementation in the Bison executables. I insist: it should be same implementation in the Bison executables. I insist: it should be
very feasible to use the very same conflict tables. very feasible to use the very same conflict tables.