The first one should report "1.618", (text) but it doesn't report at all. The second one reports it correctly.
I've no idea what the code is supposed to do but since
doesn't work (using value 63)
then its not an issue with the for loop itself
It isn't supposed to report on value 63. It's supposed to report on value 64.
Strangely, it works in visible stepping.
I'm trying to say that I don't think it's a bug with the for loop
I think its more to do with the complexity of other parts of the code
It isn't the complexity, as this doesn't work either:
And neither does this:
What do you expect a report inside a for loop to do?
To report like it does in every other primitive C-block except for FOR EACH, which seems to have the bug too:
... except that when I "result pic..." it, it does work:
And if I CALL it, it works too:
It doesn't seem to work in custom C-blocks either.
So, I found out that the scripts are stopping when they reach the report block, but they just don't report. Weird
this actually works if you use it inside a custom block, which is what REPORT is for. The gimmick that lets you view the result of a script terminated by a REPORT block is not universally supported yet.