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

* TODO (Complaint submessage indentation): New.

Browse Source
This commit is contained in:
Joel E. Denny
2009-10-06 12:47:47 -04:00
parent b143f4048f
commit 3c5362b825
2 changed files with 21 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ChangeLog
View File

@@ -1,3 +1,7 @@
2009-10-06 Joel E. Denny <jdenny@clemson.edu>
* TODO (Complaint submessage indentation): New.
2009-10-04 Joel E. Denny <jdenny@clemson.edu> 2009-10-04 Joel E. Denny <jdenny@clemson.edu>
Minor code cleanup. Minor code cleanup.

17
TODO
View File

@@ -455,6 +455,23 @@ to bison. If you're interested, I'll work on a patch.
* Better graphics * Better graphics
Equip the parser with a means to create the (visual) parse tree. Equip the parser with a means to create the (visual) parse tree.
* Complaint submessage indentation.
We already have an implementation that works fairly well for named
reference messages, but it would be nice to use it consistently for all
submessages from Bison. For example, the "previous definition"
submessage or the list of correct values for a %define variable might
look better with indentation.
However, the current implementation makes the assumption that the
location printed on the first line is not usually much shorter than the
locations printed on the submessage lines that follow. That assumption
may not hold true as often for some kinds of submessages especially if
we ever support multiple grammar files.
Here's a proposal for how a new implementation might look:
http://lists.gnu.org/archive/html/bison-patches/2009-09/msg00086.html
----- -----
Copyright (C) 2001, 2002, 2003, 2004, 2006, 2008-2009 Free Software Copyright (C) 2001, 2002, 2003, 2004, 2006, 2008-2009 Free Software