Hi again,
I believe you are onto something. This actually works!
Cheers,
Arvid
---
// Define variables
testArray = list(list([]));
testArray(1)(1).testMember = 1;
testArrayOrig = testArray;
// Define function
function outArray = testFunc(inArray)
X = inArray(1)(1);
X.testMember = 5;
OK. To me, this is a problem in the recursive insertion, which is
built-in for most native types since Scilab 6.
S.
Le 16/10/2020 à 14:55, Arvid Rosén a écrit :
Hi,
The minimal case I posted mimics the situation where the problem was
found. Removing the struct, and using just to levels of
Hi,
The minimal case I posted mimics the situation where the problem was found.
Removing the struct, and using just to levels of lists, does not trigger the
same problem. I have played around with this a bit, and yet haven’t found a
smaller case to trigger the issue.
Cheers,
Arvid
From:
Your test mix struct and lists can you reproduce it without using a struct ?
Le 16/10/2020 à 14:15, Arvid Rosén a écrit :
Hi,
I already filed a report here:
https://bugzilla.scilab.org/show_bug.cgi?id=16556
Hi,
I already filed a report here:
https://bugzilla.scilab.org/show_bug.cgi?id=16556
Do you want a more compact example than that?
Here is an even more slimmed version.
Cheers,
Arvid
--
// Define variables
testArray = list(list([]));
testArray(1)(1).testMember = 1;
testArrayOrig =
Hello,
I think that this is a sufficiently serious issue to diserve a report in
bugzilla.scilab.org. But could you prepare a more compact example ?
S.
Le 16/10/2020 à 13:35, Arvid Rosén a écrit :
Hi!
We have found a tricky issue when moving over from Scilab 5 to Scilab
6 in my
Hi!
We have found a tricky issue when moving over from Scilab 5 to Scilab 6 in my
organization. We have a lot of code which works with nested lists, and
functions modifying those lists. However, when a function is called with some
nested lists as an input argument, the body of that function
