Project

General

Profile

Bug #1139

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]

Added by Anonymous almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
01/10/2013
Due date:
% Done:

90%

Estimated time:

Description

this causes the attached error in the 2nd simulation step

simerror.png (24.8 KB) simerror.png Anonymous, 01/10/2013 01:26 PM

Related issues

Blocked by Bug #1140: during simulation, next value of an array cannot be edited, because "Invalid Type" errorClosed01/10/2013

History

#1 Updated by Anonymous almost 8 years ago

array int3 is allowed to be set to NoVal, like NoVal for normal int port. So NoVal and [NoVal, NoVal, NoVal] are both valid.

#2 Updated by Anonymous almost 8 years ago

but the simulation seems to be not able to handle this, because of the error message in the next step

#3 Updated by Anonymous almost 8 years ago

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.

#4 Updated by Anonymous almost 8 years ago

  • 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.

#5 Updated by Anonymous almost 8 years ago

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 ;)

#6 Updated by Anonymous almost 8 years ago

#1140 is also fixed.

#7 Updated by Anonymous almost 8 years ago

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.

#8 Updated by Anonymous almost 8 years ago

  • Status changed from Feedback to Resolved

#9 Updated by Anonymous almost 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF