On Monday, 12 February 2018 19:47:00 CET Ján Tomko wrote:
> On Mon, Feb 12, 2018 at 02:38:02PM +0100, Pino Toscano wrote:
> >On Tuesday, 7 November 2017 14:05:25 CET Martin Kletzander wrote:
> >> - Jansson [3] - I really like this one. The API seems very intuitive,
> >> it has
On Mon, Feb 12, 2018 at 07:47:00PM +0100, Ján Tomko wrote:
> On Mon, Feb 12, 2018 at 02:38:02PM +0100, Pino Toscano wrote:
> > On Tuesday, 7 November 2017 14:05:25 CET Martin Kletzander wrote:
> > > - Jansson [3] - I really like this one. The API seems very intuitive,
> > > it
On Mon, Feb 12, 2018 at 02:38:02PM +0100, Pino Toscano wrote:
On Tuesday, 7 November 2017 14:05:25 CET Martin Kletzander wrote:
- Jansson [3] - I really like this one. The API seems very intuitive,
it has nice documentation [4] in readthedocs (and I'm
not
On Tuesday, 7 November 2017 14:05:25 CET Martin Kletzander wrote:
> - Jansson [3] - I really like this one. The API seems very intuitive,
> it has nice documentation [4] in readthedocs (and I'm
> not talking about the visual style, but how easy is to
>
On Tue, Nov 7, 2017 at 9:34 AM, Martin Kletzander wrote:
> On Tue, Nov 07, 2017 at 01:38:51PM +, Richard W.M. Jones wrote:
>>
>> On Tue, Nov 07, 2017 at 01:28:00PM +, Daniel P. Berrange wrote:
>>>
>>> On Tue, Nov 07, 2017 at 02:05:25PM +0100, Martin Kletzander wrote:
On Tue, Nov 07, 2017 at 01:28:00PM +, Daniel P. Berrange wrote:
On Tue, Nov 07, 2017 at 02:05:25PM +0100, Martin Kletzander wrote:
Hi everyone,
so we are using yajl for parsing JSON. However there are some reasons
why we might consider switching to another one:
1) It is basically dead
On Tue, Nov 07, 2017 at 01:38:51PM +, Richard W.M. Jones wrote:
On Tue, Nov 07, 2017 at 01:28:00PM +, Daniel P. Berrange wrote:
On Tue, Nov 07, 2017 at 02:05:25PM +0100, Martin Kletzander wrote:
> 4) The are workarounds for it in the code
I don't recall what these are now ?
I
On Tue, Nov 07, 2017 at 01:28:00PM +, Daniel P. Berrange wrote:
> On Tue, Nov 07, 2017 at 02:05:25PM +0100, Martin Kletzander wrote:
> > 4) The are workarounds for it in the code
>
> I don't recall what these are now ?
libguestfs needs to disable some warnings around yajl code:
/* GCC
On Tue, Nov 07, 2017 at 02:05:25PM +0100, Martin Kletzander wrote:
> Hi everyone,
>
> so we are using yajl for parsing JSON. However there are some reasons
> why we might consider switching to another one:
>
> 1) It is basically dead upstream
One could say that it is simply "feature complete"