Structured output?

[Mike Frysinger]

On Thursday, February 06, 2014 15:41:54 Philippe Ombredanne wrote:
> - whatever the api used, it should be able to print the exact same
> format as today pixel per pixel ;)  and support ideally only one new
> structured format for now.
> 
> - I have no special preference for a format, except that I prefer text
> over binary and that this should be a standard well-defined format
> with plenty of available support in most languages. Of text formats,
> using some CSV-like would still be flat (short of inventing a
> non-standard way of nesting data) and would likely be a regression
> from the current format; XML is likely too verbose; yaml structure
> requires multiple lines; Json is a tad verbose but less so than XML
> and a list entry can be packed on a single line. So a json-like format
> is likely a good candidate but this is not really super friendly for
> piped input processing with common shell tools (though the current
> strace output is more or less there for that today).

make it JSON.  every language out there can ingest JSON easily.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20140208/1db58a2b/attachment.bin>