Menu
The comma , items separator used in an array initialization list may end the list in C, this is mentioned in The C Programming Language 2nd ed by Kernighan & Ritchie .
e.g.
int c[] = { 1, 2, 3, };
This is convenient when the list is long, and one doesn't want to have to change/check the previous line when adding items
long long c[] = {
22342342344,
4324234234,
12312311111,
};
However in Java I could observe two different behaviors:
In Eclipse, the ending , is accepted while some versions of the maven compiler plugin complain and throw a compilation error.
However, I didn't find any mention of this singularity in the Flanagan's Java book.
What is the official rule regarding an ending comma after the initialization items?
Is it recommended not to use it?
516
JavaScript allows trailing commas wherever a comma-separated list of values is accepted and more values may be expected after the last item. This includes: Array literals.
To initialize or instantiate an array as we declare it, meaning we assign values as when we create the array, we can use the following shorthand syntax: int[] myArray = {13, 14, 15}; Or, you could generate a stream of values and assign it back to the array: int[] intArray = IntStream.
We can declare and initialize arrays in Java by using a new operator with an array initializer. Here's the syntax: Type[] arr = new Type[] { comma separated values }; For example, the following code creates a primitive integer array of size 5 using a new operator and array initializer.
In Java, all array elements are automatically initialized to the default value.
Section 10.6 of the spec explicitly says that a trailing comma is allowed (and ignored):
A trailing comma may appear after the last expression in an array initializer and is ignored.
Link
192
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
