[Top][All Lists]

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

[Octave-patch-tracker] [patch #9980] JSON encoder and decoder, alternati

From: anonymous
Subject: [Octave-patch-tracker] [patch #9980] JSON encoder and decoder, alternative to object2json
Date: Mon, 29 Nov 2021 13:37:23 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0

Follow-up Comment #43, patch #9980 (project octave):


I'm reviewing my notes.

I would be happy to fix the problem, but as I noted before, I'm unable to
replicate the bug.  As far as I can tell, it doesn't seem to be a problem in
current release (6.4).  If it is, then I really need help replicating error. 
I've tried number of different methods to import and parse non-UTF-8 encoded
JSON strings but couldn't generate an error from "fromJSON".  

Anyways, regarding encoding issue specifically, I'm hesitant to let regexp
error propagate (i.e. drop the try-catch).  While I agree that the meaning of
the error is clear, it allows the end-user to presume that the solution is
found in modifying "fromJSON" rather than dealing with input string.  

If your concern about the exact wording of error, I'm fine with modifying it
in line with your suggestion.  

On the issue of pointing to the offending char, I agree it would be nice to
have, but you rightly point that this is a regexp-issue and as such beyond the
scope of "fromJSON".

Give me a couple more days to try to get Oct 7 built and try to replicate
error myself.



Reply to this item at:


  Message sent via Savannah

reply via email to

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