[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
TODO
From: |
Akim Demaille |
Subject: |
TODO |
Date: |
22 Oct 2002 13:19:34 +0200 |
User-agent: |
Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter) |
Index: TODO
===================================================================
RCS file: /cvsroot/bison/bison/TODO,v
retrieving revision 1.82
diff -u -u -r1.82 TODO
--- TODO 19 Oct 2002 14:39:07 -0000 1.82
+++ TODO 22 Oct 2002 11:19:25 -0000
@@ -12,18 +12,6 @@
find something clean (not like YYLSP_NEEDED...).
-* readpipe
-
-It should be replaced to avoid tmp files and to improve portability.
-Also, as it is it does not call error () when execve fails, and
-therefore, running M4='m4 --version' bison will silently fail instead
-of:
-
- bison: cannot run m4 --version: No such file or directory
-
-BTW: I would really like to be able to pass arguments to m4...
-
-
* URGENT: Documenting C++ output
Write a first documentation for C++ output.
@@ -41,17 +29,6 @@
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.
@@ -109,6 +86,17 @@
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
@@ -210,8 +198,11 @@
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 <address@hidden> 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
[Prev in Thread] |
Current Thread |
[Next in Thread] |