[Scilab-users] bug when setting gcbo field in a callback function ?

[Samuel Gougeon]

Le 29/09/2018 à 00:31, antoine monmayrant a écrit :
> Hello Stéphane,
>
> Well, I tried exactly this trick with mixed results: it kind of works 
> most of the time, but sometimes it fails.
> I did not manage to reproduce the issue with my minimum working 
> example though.
>
> It's weird, no?
> Why would gcbo behave differently than h?
>
> As for why "set" is working, while "gcbo.whatever=something" is 
> failing, I think it's because something goes wrong when scilab is 
> parsing "gcbo.whatever=something".
> It is as if scilab forgot about the fact that gcbo exists and does 
> what we expect when creating a struct:
>     doesnotexists.whatever=something;
> creates a "doesnotexists" struct with one field==something.

This bug exists at least since Scilab 5.3.3 (not tested with older 
versions) and is not yet reported.

Samuel