The list was things that make lists, which are the problematic things Scalar/List context-wise. At that point I was summarising what had been discussed so far...

But you had discussed arrays and hashes. Are you implying that array slice make lists and arrays don't?

The omission seems rather "convenient" because it allowed you to cut two exceptions from the "in Scalar Context" list.

Given that an array returns a list in list context, how do you place that list in scalar context?

I would argue that, when treated as an rvalue, this is the key difference between a list and an array. Since in Scalar Context the value of the array isn't the list, the case does not arise.

Exactly. A list can't be produced in scalar context. So how can a list be put into scalar context?

The point of the question was to point out that "list" is an overloaded term. "List in scalar context" is deceptive, misleading and/or confusing.

Ah. I had expected the second, scalar assignment, to operate on the result of the first assigment.

Assignment operators are right-associative. That means that in chain of assignments, the right-most has highest precedence. ** is also right-associative.

>perl -le"print( 2**3**4 )"
2.41785163922926e+024

>perl -le"print( (2**3)**4 )"
4096

>perl -le"print( 2**(3**4) )"
2.41785163922926e+024
[download]

OK. Well, everybody avoided mentioning the influence of Scalar Context on arrays.

Two of the three types of list I mentioned in my answer can't be put into scalar context. That makes it a rather minor difference.