X-Git-Url: https://git.saurik.com/bison.git/blobdiff_plain/0164db681e22e56db4b01990e72b335b66f48197..9306c70c63e750e69133237407b303c1fa404554:/TODO diff --git a/TODO b/TODO index 779cf9e5..1c7c9f77 100644 --- a/TODO +++ b/TODO @@ -269,8 +269,13 @@ It is unfortunate that there is a total order for precedence. It makes it impossible to have modular precedence information. We should move to partial orders. +This will be possible with a Bison parser for the grammar, as it will +make it much easier to extend the grammar. + * Parsing grammars -Rewrite the reader in Bison. +Rewrite the reader in Flex/Bison. There will be delicate parts, in +particular, expect the scanner to be hard to write. Many interesting +features cannot be implemented without such a new reader. * Problems with aliases From: "Baum, Nathan I" @@ -318,7 +323,6 @@ everything, but the -v mode only tells you what you need for examining conflicts? (Or, perhaps, a "*** This state has N conflicts ***" marker above each state with conflicts.) - * $undefined From Hans: - If the Bison generated parser experiences an undefined number in the @@ -341,12 +345,21 @@ $$ = $1. I therefore think that one should implement a Bison option where every typed default rule is explicitly written out (same typed ruled can of course be grouped together). +Note: Robert Anisko handles this. He knows how to do it. + +* Documenting C++ output +Write a first documentation for C++ output. + * Warnings It would be nice to have warning support. See how Autoconf handles them, it is fairly well described there. It would be very nice to implement this in such a way that other programs could use lib/warnings.[ch]. +Don't work on this without first announcing you do, as I already have +thought about it, and know many of the components that can be used to +implement it. + * Pre and post actions. From: Florian Krohm Subject: YYACT_EPILOGUE