Hello ikegami,

I had to think carefully about this, but of course you’re right. Without parentheses:

13:54 >perl -MData::Dump -wE "my @c = 2, 3; dd \@c;"
Useless use of a constant (3) in void context at -e line 1.
[2]

16:15 >
[download]

the assignment occurs first, because the precedence of the assignment operator is higher than that of the comma operator. So the fact that assignment to an array puts the right-hand side into list context is irrelevent here. With scalar context imposed instead:

16:35 >perl -wE "my $c = 2, 3; say $c;"
Useless use of a constant (3) in void context at -e line 1.
2

16:36 >perl -wE "my $c = (2, 3); say $c;"
Useless use of a constant (2) in void context at -e line 1.
3

16:36 >
[download]

the parentheses act only to change the order of evaluation, because parenthesized expressions (“terms”¹) have the highest precedence. So in a standard array assignment:

16:36 >perl -MData::Dump -wE "my @c = (2, 3); dd \@c;"
[2, 3]

16:36 >
[download]

the assignment to an array puts the RHS into list context; the parentheses create a term; and within that term, the comma operator is “just the list argument separator, and inserts both its arguments into the list.”² I think that makes sense. :-)

Thanks for the clarification,

¹perlop#Terms-and-List-Operators-(Leftward).
²perlop#Comma-Operator.