Bug? accessing LOCAL var in shared scope

[lenborje]

I have been using LOCAL vars declared outside the programs, to get the equivalent of variables shared between routines in the same program, but not exported globally.

There is something strange going on whenever I try to use these variables as function arguments; they are not accessed at all. I always have to copy them to a local variable first. Example:

Code:

LOCAL foo=[[1,2],[3,4]];
EXPORT GlobalVarIgnored()
BEGIN
  PRINT();
  PRINT(foo);
  PRINT(colDim(foo));

  LOCAL bar=foo;
  PRINT(bar);
  PRINT(colDim(bar));
END;

I would expect both PRINT(colDim(foo)) and PRINT(colDim(bar)) to print out same number (2), but instead the output of the program is:

Code:

[[1,2],[3,4]]
colDim(foo)
 Error: Bad Argument Value
[[1,2],[3,4]]
2

What's going on? Is this a bug or have I missed something?

(Discovered in 6030; confirmed in 6940.)