|Problems? Is your data what you think it is?|
Re^3: (RFC) Arrays: A Tutorial/Referenceby chromatic (Archbishop)
|on Jan 13, 2007 at 19:23 UTC||Need Help??|
I guess they do.
I hate being cruel... but read the parser.
Or is that also a kind of disambiguation (of the match operator)?
In one sense, those parentheses only mark the empty list, but it's probably more accurate to say that those do create a list. That's only true for the empty list however, as parsers have a very difficult time identifying invisible, non-existent characters.
Hmm.. here they obviously don't force list context?
Correct. Why would you expect them to do so? They're immaterial to the expression, just as in my $x = ( 2 + 2 );.
If parentheses did create lists, what would you expect this code to do?my $x = ( 1 + 2 ) * 3;
Perl doesn't have a strict leftmost-applicative evaluation order, so the parentheses are necessary to disambiguate precedence.
That's the exact reason why the parentheses are necessary to group lists, but do not create lists. In:my @fib_values = 1, 1, 2, 3;
... the expression my @fib_values = 1 is a complete expression to the parser as it is. Now it may be completely unambiguous to you that the entire expression is a list assignment, but there are plenty of more complicated assignment forms that involve mixed expressions such that Perl will give you a warning that it may have guessed wrong in this case.
Note also that you don't need parentheses when passing an argument list to a function or especially a built-in operator... again, unless you need to disambiguate something.