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

[Andrew Janke]

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

Hi Qianqian! Thanks for chiming in.

I think that JSONlab and my jsonstuff package could happily co-exist. The goal
of jsonstuff is simply to create Matlab-compatible implementations of
jsonencode/jsondecode for Octave. My impression is that jsonencode/jsondecode
is to allow Matlab to access external APIs that provide data in "native" JSON
format. It doesn't cover more general or flexible JSON handling, or persisting
of arbitrary Matlab data structures to JSON, like your JSONlab does. My goal
is to eventually get jsonstuff merged into core Octave and cease to have it be
an independent package.

I have no intention of expanding jsonstuff beyond the base
jsonencode/jsondecode, or (probably) even supporting the Matlab Production
Server JSON format, since that's not available in base Matlab, and as far as I
know, MPS interoperability isn't an Octave design goal. jsonstuff's goals are:
1) Matlab-compatible jsonencode/jsondecode, 2) decent performance, and 3)
nothing else.

I'll take a look at your JData stuff when I have some spare time; I'm pretty
busy with the day job and a conference right now. Offhand, I think support for
extended JSON functionality like that should probably stay independent from
Octave's jsonencode/jsondecode stuff: since that's not provided by base Matlab
either, it seems suited for a package that would work in both Matlab and
Octave.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?53100>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/