* src/system.h: Include sys/types.

[bison.git] / TODO

diff --git a/TODO b/TODO
index b21ed19fde0ac7cbb93c7e6288698d057765c5e5..436fa0d38c48049db13d4e5154c56ff821ff7db9 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,5 +1,17 @@
 -*- outline -*-
 
+* Header guards
+
+From Franc,ois: should we keep the directory part in the CPP guard?
+
+
+* Yacc.c: CPP Macros
+
+Do some people use YYPURE, YYLSP_NEEDED like we do in the test suite?
+They should not: it is not documented.  But if they need to, let's
+find something clean (not like YYLSP_NEEDED...).
+
+
 * URGENT: Documenting C++ output
 Write a first documentation for C++ output.
 
@@ -17,15 +29,8 @@ Some are really funky.  For instance
 is really weird.  Revisit them all.
 
 
-* read_pipe.c
-This is not portable to DOS for instance.  Implement a more portable
-scheme.  Sources of inspiration include GNU diff, and Free Recode.
-
-
-* value_components_used
-Was defined but not used: where was it coming from?  It can't be to
-check if %union is used, since the user is free to $<foo>n on her
-union, doesn't she?
+* GLR & C++
+Currently, the GLR parser cannot compile with a C++ compiler.
 
 
 * Report
@@ -81,6 +86,17 @@ When implementing multiple-%union support, bare the following in mind:
          char *sval;
        }
 
+** %if and the like
+It should be possible to have %if/%else/%endif.  The implementation is
+not clear: should it be lexical or syntactic.  Vadim Maslow thinks it
+must be in the scanner: we must not parse what is in a switched off
+part of %if.  Akim Demaille thinks it should be in the parser, so as
+to avoid falling into another CPP mistake.
+
+** -D, --define-muscle NAME=VALUE
+To define muscles via cli.  Or maybe support directly NAME=VALUE?
+
+
 * Unit rules
 Maybe we could expand unit rules, i.e., transform
 
@@ -110,11 +126,22 @@ 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:
 
+** Java
+
+There are a couple of proposed outputs:
+
+- BYACC/J
+  which is based on Byacc.
+  <http://troi.lincom-asg.com/~rjamison/byacc/>
+
+- Bison Java
+  which is based on Bison.
   <http://www.goice.co.jp/member/mo/hack-progs/bison-java.html>
 
+Sébastien Serrurier (serrur_s@epita.fr) is working on this: he is
+expected to contact the authors, design the output, and implement it
+into Bison.
 
 
 * Coding system independence
@@ -171,8 +198,11 @@ Some users create their foo.y files, and equip them with #line.  Bison
 should recognize these, and preserve them.
 
 * BTYacc
-See if we can integrate backtracking in Bison.  Contact the BTYacc
-maintainers.
+See if we can integrate backtracking in Bison.  Charles-Henri de
+Boysson <de-boy_c@epita.fr> is working on this, and already has some
+results.  Vadim Maslow, the maintainer of BTYacc was contacted, and we
+stay in touch with him.  Adjusting the Bison grammar parser will be
+needed to support some extra BTYacc features.  This is less urgent.
 
 ** Keeping the conflicted actions
 First, analyze the differences between byacc and btyacc (I'm referring