* TODO (Complaint submessage indentation): New.

diff --git a/ChangeLog b/ChangeLog
index 90f6c23d452ba6687f73b8f2b085fe42279f68fb..5bbab03ab73c0f718374e1a12f6b708bd9ac9599 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -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>
 
        Minor code cleanup.
 2009-10-04  Joel E. Denny  <jdenny@clemson.edu>
 
        Minor code cleanup.

diff --git a/TODO b/TODO
index c3aac3172ecea9b85a1bd07eeec7828589a60ff0..7f4c514898c84927621fc78cbf4db027012c41aa 100644 (file)
--- a/TODO
+++ b/TODO
@@ -455,6 +455,23 @@ to bison. If you're interested, I'll work on a patch.
 * Better graphics
 Equip the parser with a means to create the (visual) parse tree.
 
 * Better graphics
 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