[Octave-bug-tracker] [bug #63199] [feature request] add a function to inverse eval() function

[Yu Hongbo]

Follow-up Comment #4, bug #63199 (project octave):

bug #1: eval() function will parse an expression, even this expression is
meant to be a function handle. Users will consider the context when they need
to use eval() function, so developers don't need to help making this kind of
desicion. I give a scenario about transferring any kind of Octave variants:
Remote procedure call (RPC) is a distributed computing technology, it is used
to transfer a procedure to another device. The current jsonencode() and
jsondecode() logic cannot transfer any kind of Octave variants, so Octave
cannot fully transfer the current to another remote Octave instance with the
two functions.

bug #2: I expect 
>> jsondecode('[{},{}]')
and
>> jsondecode('[[{}],{}]')
and
>> jsondecode('[[{}],[{}]]')
should return different results, and the results should be used to rebuild the
original data.
Why care about which jsonencode command? This is a legal JSON text.

bug #3: The document only mentioned null, inside a numeric array and null,
inside a non-numeric array. So how about null outside an array? I don't see
this document.


    _______________________________________________________

Reply to this item at:

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

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