Date: Tue, 10 Jun 2014 22:58:26 -0700 From: Eitan Adler <lists@eitanadler.com> To: Zaro Korchev <zkorchev@mail.bg> Cc: soc-status@freebsd.org Subject: Re: [Machine readable output from userland utilities] report Message-ID: <CAF6rxgk48f=ZvzujLw=4UqiMvuiBHZjA-JAT_Pz56QxvmLzJdw@mail.gmail.com> In-Reply-To: <2F779B73-EAC5-49B4-B3E8-7A81109EC166@mail.bg> References: <8D1B686D-1AAA-4E07-9270-E42699110561@mail.bg> <2F779B73-EAC5-49B4-B3E8-7A81109EC166@mail.bg>
next in thread | previous in thread | raw e-mail | index | archive | help
Sweet! On 9 June 2014 06:22, Zaro Korchev <zkorchev@mail.bg> wrote: > Hi everybody > > This week I continued adding structured output capabilities to packages. > > I have modified fstat in the base system. I have also a lot of work done = on netstat but it's pretty big and so I'm not finished with it yet. > I made a macro that simplifies using string leterals as map keys in libso= l. I'm in the process of making the tools I have already converted use it. = This will slightly reduce the complexity of the code and hopefully decrease= the amount of possible bugs : Cool. > Most of the changes I have committed to the svn server (I have left out t= he changes that don't compile at the moment). > One issue I encountered is that currently some integers are displayed in = hexadecimal but it's possible that the underlying output format does not su= pport hexadecimal integers (as is the case with JSON). At the moment I'm ju= st displaying them as decimal numbers. I would be glad to hear if somebody = has a better suggestion. I think its okay to output this as a string literal too. This is up to you and likely depends on how much work it would take to support this. --=20 Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAF6rxgk48f=ZvzujLw=4UqiMvuiBHZjA-JAT_Pz56QxvmLzJdw>