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

[Philip Nienhuis]

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

(io pkg maintainer here)

Yes, I'd happily accept compiled JSON stuff, but I'm afraid I can't maintain
it due to lack of knowledge about JSON - so maintenance is left to
contributor(s).
Are we sure the io package is a good home for it? If yes, good, if no, maybe
miscellaneous could be better, I really don't know. Opinions?

If it introduces a new dependency I'd prefer to make it a "soft" dependency -
if the io package is installed (built) and the underlying JSON lib is absent,
the pkg should be installed w/o the JSON functions depending on that library,
please with a suitable message.
As an example, Carnë created a particularly luxurious version for gdalread in
the mapping package and the GDAL library. IMO it need not be that slick but
something along those lines would be nice, the bottom line is users do need to
know and be able to find out if their io package installation supports the
JSON stuff or not.

OTOH if the JSON library is not too big, comprises a limited nr. of files, and
has a GPL compatible license, it can be included in, and shipped with, the io
package. JuanPi and I did s/th similar for the clipper polygon clipping
library in the geometry package.

Maybe then the existing JSON .m-file function could be replaced by faster
compiled ones?


    _______________________________________________________

Reply to this item at:

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

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