Support #975: Usability Testing and Feedback
Support #1108: Testing the implementation of arrays
during simulation, array[ 3 ] is set to NoVal and not to [NoVal, NoVal, NoVal]
this causes the attached error in the 2nd simulation step
array int3 is allowed to be set to NoVal, like NoVal for normal int port. So NoVal and [NoVal, NoVal, NoVal] are both valid.
but the simulation seems to be not able to handle this, because of the error message in the next step
as discussed last time, if array access or structure access is performed on NoVal, it's a semantic error and shall be fixed by user. It uses the same principle like NullPointerException in Java.
- Status changed from New to Feedback
- Assignee changed from Anonymous to Anonymous
- % Done changed from 0 to 90
fixed codes which produces wrong expressions in dialog.
ok, the error message in the dialog is much more helpful now.
However, due to issue #1140, I am still not able to define the next value of the array in order to get rid of the error-dialog ;)
Let Input have a type array and it is NoVal. Then we CANNOT access its members !!!
Furthermore, the members of an array are VALUES and they cannot be NoVal.
- Status changed from Feedback to Resolved
- Status changed from Resolved to Closed
Also available in: Atom