> As for the generation code: in my experience, this is harder than it seems > because (among other things) the APIs one would need depend on the way the > utility producing the output is structured -- many existing utilities are > built to print the data a cell at a time, whereas others print a row at a > time, and still others gather all the information first and then print a > table. That said, I have built some mostly-generic row-at-a-time routines > for ipmpstat that I'd be willing to generalize further and package up into > a reuseable API if folks are interested. But it's not easy to create a > simple API that completely separates the parsing machinery from the data
Sorry, I meant to say "output machinery". Note that the API handles all aspects of output, not just parseable output. > collection, so I'd like to get some more experience with it and later run > it as a follow-on case. > > [1] For instance, show-link has a unique key of LINK, whereas > show-linkprop requires LINK and PROPERTY to form a unique key. -- meem
