[Octave-patch-tracker] [patch #9980] JSON encoder and decoder, alternative to object2json

[Philip Nienhuis]

Update of patch #9980 (project octave):

                  Status:                    Done => Need Info              
             Open/Closed:                  Closed => Open                   

    _______________________________________________________

Follow-up Comment #42:

(reopening temporarily)

I'm about to prepare an io-2.6.4 release so was looking at this item in
comments #38-40 that is still on my "io" to-do list.

What's the advice? just drop the try-catch block cf. comment #38? or change
the error message into s/th along the lines of:

error ("Maybe invalid UTF-8 encoding of JSON string ?");


Maybe even throw lasterr before the error message? (actually equivalent to
dropping the try-catch)

I'm with Markus in that it's probably better to just let regexprep show its
error message followed by the stack trace. But for the situation at hand, is
regexprep's error message clear enough when it crashes due to encoding issues?
I just don't know.

On another note, when hitting errors while parsing strings I find it often
handy if the location of the offending characters in the string is returned.
But that may be asking too much here :-) (I suppose that would be regexprep's
job)

(sattus => need info)

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?9980>

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