Error: Wrong number of subscripts in number[eqn2] (1 subscripts for 0 dimensions)

[Lennart Ochel]

It is often needed to use arrayGet in for loops to avoid strange errors if array elemts get accessed via iterator directly.

for eqn2 in mT[var] loop
  if number[eqn2] == -1 then
    [...]
  end if;
end for;

The snippet above generates following error Message:

Error: Wrong number of subscripts in number[eqn2] (1 subscripts for 0 dimensions).

This can be avoided if number[eqn2] get replaced by arrayGet(number, eqn2).

[Adrian Pop]

Per, can you have a quick look at this?

[Lennart Ochel]

BTW: Is there a good reason that it is needed to use arrayUpdate instead of writing to an array element via squared bracket syntax?

[Per Östlund]

Replying to lochel:

BTW: Is there a good reason that it is needed to use arrayUpdate instead of writing to an array element via squared bracket syntax?

No, there's no good reason for that. I'm trying to fix it, but the compiler does weird things with subscripted crefs.

[Per Östlund]

All right, fixed in r25678, both accessing and assigning arrays using the bracket syntax should work now. It turned out that someone had already implemented code generation for assignment to MetaModelica array crefs, but because of a typo it was never used.

[Lennart Ochel]

Should it be possible to write to arrays using the bracket syntax that are inputs, since it is possible using arrayUpdate?

[Per Östlund]

Replying to lochel:

Should it be possible to write to arrays using the bracket syntax that are inputs, since it is possible using arrayUpdate?

Yes, subscripted MetaModelica arrays are converted into the appropriate arrayUpdate/arrayGet calls in the code generation depending on which side of the assignment they are on.

[Dietmar Winkler]

It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.

[Martin Sjölund]

Removing the pre1.9.4 milestone in favor of 1.9.4.