[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53100] implement jsondecode, jsonencode funct

From: Andrew Janke
Subject: [Octave-bug-tracker] [bug #53100] implement jsondecode, jsonencode functions
Date: Sat, 2 Feb 2019 03:50:07 -0500 (EST)
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Follow-up Comment #10, bug #53100 (project octave):

I agree: this should end up in Octave core, since these are core (non-toolbox)
Matlab functions. Just, uhh, gimme a moment to shake out the bugs.

Supporting multiple parser library back-ends might make this a lot more
complicated – JSON is a super simple format, and as such the parser
libraries have really simple interfaces, but they're not at all the same
interface. Writing a compatibility layer to switch between different parser
library back-ends at run- or compile-time might be more complicated than the
whole rest of this library. IMHO.

I looked at rapidjson - that looks really cool. I think I'd be down to switch
it out for JsonCpp here, if folks have a preference. But I dunno about
supporting both/either: that compatibility/flexibility would mean a lot of

If people actually care, maybe I could code up an alternate version using
rapidjson and we could discuss which one we prefer, and then pick one?


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]