Open kwollw opened 5 years ago
see #74
see #215
still an issue, not solved in #215
proposed solution: null may only be used for reference types. Constrains should be checked in blockly and visitor
proposed solution: null may only be used for reference types. Constrains should be checked in blockly and visitor
I think that this is a good idea, since it would also fix another bug: If you try to assign 'null' to a number variable using lejos, you get a compilation error:
If you want I can work on this issues. The only question I have is if the solution should apply to blockly and visitor of only Caliope (and maybe lejos) or to all the robots.
given the following NEPO program for Calliope:
At the calliope board "Zeige Text x" displays "1" but the simulation displays "undefined".
Without initialialization of "null" the simulation works correctly.
It should be expected that board and simulation show identical behavior.