Project

General

Profile

Feature #1137

Support #975: Usability Testing and Feedback

Support #1108: Testing the implementation of arrays

Error-Marker on using Arrays and native Variable in one Term in the Code-Specification

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

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

100%

Estimated time:

Description

My component has 2 input and 1 output port:

in1 of type int-array[ 5 ]
in2 of type int
out1 of type int

However, using:
out1 = in1[ 0 ] + in2;

results in an error "Type mismatch in code specification of component Adder".

See attached *.af3_20 project

struct_and_array_test.af3_20 (10.9 KB) struct_and_array_test.af3_20 Anonymous, 01/10/2013 12:07 PM
struct_and_array_test.af3_20 (11 KB) struct_and_array_test.af3_20 new test project file Anonymous, 01/10/2013 12:50 PM

Related issues

Precedes Feature #1173: Code specification: On-the-fly type-checks and errors reporting in code specificationsClosed01/17/2013

History

#1 Updated by Anonymous almost 8 years ago

fixed type checker problem. Type check logic will be fixed in Issue 1132

#2 Updated by Anonymous almost 8 years ago

  • Description updated (diff)

#3 Updated by Anonymous almost 8 years ago

it isn't shown an error if I access a 1 dimensional array in a 2 dimension style "Input1IntArray[ 0 ][ 2 ]"

#4 Updated by Anonymous almost 8 years ago

  • Tracker changed from Bug to Feature
  • Assignee changed from Anonymous to Anonymous
  • % Done changed from 70 to 30

Currently, code specification editor only checks the grammar of the input. No type checking is performed. In order to check mismatched type access like "(int)output = (MyArray)input" or invalid dimension access, a systematical type checking mechanism with detailed violation reports is required. I think it is more as a feature than a bug. Shall we implement this feature?

#5 Updated by Anonymous almost 8 years ago

  • Status changed from In Progress to Closed

I think that this is a bigger issue - I've created Issue #1173 (feature). For RC3 we can close this bug and live with this limitation.

#6 Updated by Anonymous almost 8 years ago

  • % Done changed from 30 to 100

Also available in: Atom PDF