I know it's valid syntax to declare an array like the following

double[] something = {

1.1,

2,2,

2,3,

}

Is it possible to generate a warning or error for the uninitialized value after the trailing comma?

Why would you want that though? It has no adverse effect and just makes it easier to add new elements if you're still working on the code.

I actually use AngelScript for a real time engine test cell controller. One of the users of my application created an array of engine speeds like so

EngineSpeed[] ={

1000,

2000,

3000,

4000,

5000,

6000,

}

The test sequence that was written uses the array size function to loop through each speed. The uninitialized element had a value of x^219 (thankfully engines can't actually go that fast). There should have been a check to see that the speed was within limits but the uninitialized value could have been any valid engine speed as well. I was just looking for a way to issue a warning or error as an additional check to let the user know they made a mistake.

I'm not sure about AngelScript, but languages that permit trailing commas normally make arrays like:

EngineSpeed[] ={
1,
2,
3,
}

...contain 3 elements, not 4 elements with an uninitialized value. Sounds like a bug in AngelScript.

That being said, the bug could be in your code. Here's what you posted:

double[] something = {
1.1, //ONE element. You have a period here, not a comma. Did you mean "1,1" instead of "1.1"
2,2, //Two elements.
2,3, //Two elements.
}
//The array generated should be 5 total {"1.1", "2", "2", "2", "3"}

Is it possible your code is assuming the array size is multiples of two, and so is accidentally accessing one past the end of the array?

The extra comma's were typos. If you execute the following the AngelScript code:

You will get a length of 4 and a random number for index 3. This is what I got on my machine. The value is just a random number.

2014-10-04 4:01:05 PM Length of Speed = 4 Speed[3]= 9.88131e-324

I wish the array would default to a size of 3 and ignore the last value.

This is also valid code and will result in a length of 7.

Oh, I wasn't aware of this. Very strange. I've never used another language with that behavior...sounds like it probably does more harm than good, no? You can always pass null or 0 if you want to have uninitialized elements in your array.

Why would you want that though?

I know why i would.

Not long ago i got a weird crash when loading bytecode containing funcdef array with extra comma. Nothing tried to access last element, couldn't reproduce it, happens only on linux version of application... I'd enable it just to make sure other scripters don't screwup anything - finding single comma in big codebase is not fun at all :]

Totally understandable -- my comment was based on the assumption that Angelscript was like every other language I've used and that a trailing comma didn't make any difference at all.

I'll add an engine property to allow the application developer to decide how empty elements in initialization lists should be treated by the compiler.

Regards,

Andreas

I've added the engine property asEP_DISALLOW_EMPTY_LIST_ELEMENTS in revision 2050. Set it to true to tell the compiler to give an error on empty elements (but ignore the last comma in lists with variable length).

Thanks,

Andreas