In the help/Introduction/Literals there are two examples of the array value type:

 -  ['This','is','a','string','array','literal']
 - [100,2,45]

So I tried

const
 s1 = ['This','is','a','string','array','literal'];
 s2 = [100,2,45];

and get a compiler error

 -  "[Error]: Duplicate identifier declaration array of ".

Of what? There is a training blank in the error string. Where is my mistake?

Michael Dreher

Michael Dreher wrote:

> const

Shouldn't that be var?

--

Matthew Jones

"Matthew Jones" wrote:

 // > const
 // Shouldn't that be var?

In the library code I've found examples, where array literals are assigned to local vars (WebCore.isDay for example). But then the help defines:

 // <Constant Declaration> =
 //      <Constant Name> = <Expression>
 //
 // The <Expression> element can be any valid expression that does not contain any variable, function,
 // or procedure references. In other words, the expression can only contain other constant references,
 // or literal expressions.

And on a global scope I'd ensure the values are not modified, hence const.
Interesting: s1 and s2 can be compiled without errors, but mutually exclusive and not together.

Michael Dreher

Michael Dreher wrote:

> Interesting: s1 and s2 can be compiled without errors, but mutually
> exclusive and not together.

In which case, report it to Tim via email with a sample project. Sounds
like a compiler issue.

--

Matthew Jones

"Matthew Jones" wrote:

 // In which case, report it to Tim via email with a sample project. Sounds
 // like a compiler issue.

That's why I already attached the project code in my first post of this thread

Michael Dreher

Michael,

<< In the help/Introduction/Literals there are two examples of the array value type:

 -  ['This','is','a','string','array','literal']
 - [100,2,45]

So I tried

const
 s1 = ['This','is','a','string','array','literal'];
 s2 = [100,2,45];

and get a compiler error >>

Those are variable examples, and apparently the compiler is having an issue with using them in a const section.  I'll check it out.

Tim Young
Elevate Software
www.elevatesoft.com

Michael,

No, it wasn't the const section, it was the way that the compiler was naming array types that are created "on-the-fly" for use in one-offs like consts.

It's now fixed.

Tim Young
Elevate Software
www.elevatesoft.com