[ovs-dev] [RFC] Output refactor for customized displays

[Ben Pfaff]

On Fri, Nov 18, 2016 at 05:22:27PM -0500, Aaron Conole wrote:
> During some recent face-to-face talks regarding debugging ovs, an issue
> was raised regarding the output.  The gist of the conversation was that as
> it stands, ovs output is less-than-friendly, and a different output would
> be helpful.
> 
> Looking a bit into it, it appears that the output routines for most of the
> openflow / ovs data uses the dynamic string library to just append as much
> structure data as possible, in whatever form was originally useful.  This
> is fine for ovs wizards, but some 'mere mortals' would prefer prettier
> output with the ability to tweak / omit the data that comes out of the tools.

I like the idea of a table printing framework, but can you explain why
this library is separate from the one in lib/table.[ch]?