On Tue, Mar 11, 2014 at 6:36 AM, Mike Frysinger <vap...@gentoo.org> wrote: > On Mon 03 Mar 2014 10:26:22 Philippe Ombredanne wrote: >> or possibly (not sure which form I like best) using a more compact >> entirely and positional list of lists: >> [ >> "open", >> "-1", >> [ >> "/usr/lib/locale/UTF-8/LC_CTYPE", >> "O_RDONLY|O_CLOEXEC" >> ] >> ] > > that's a good way to not be future-proof. considering you're already > serializing to json, adding a few extra fields to keep things sane isn't > really going to hurt.
Good point. So let's go with explicit field names, except for things like "call_one" "call_two" that really do not make sense. i.e. the top level structure should likely be a list of calls. > if performance is an issue, that's where a binary output format would come in > rather than making the json so terse as to be a pita to maintain. especially > considering the point is to make an interface that other tools can build on > top of sanely, and breaking the json output straight up isn't useful. > > although quibbling over the exact output format doesn't really matter to the > internal design aspects (which is the majority of the work is going to be > anyways). the strace code base would have a framework to call an output > module and that would take care of the exact output details. It is the goal indeed! -- Philippe Ombredanne ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
