in reply to Re^6: What's most efficient way to get list context? (count)
in thread What's most efficient way to get list context?

A slice is an operator, yet another kind of "node" using my terminology up-thread. A slice in a list context does the listy thing. A slice in a scalar context returns the last element, but could have been made to invoke nethack again. It has nothing to do with the comma operator, which has its own scalar/list behavior.

The only consistency is that Larry made some of them consistent. It's DWLM: "Do What Larry Means". But it is learnable, and does make sense once you learn it.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

  • Comment on Re^7: What's most efficient way to get list context? (count)

Replies are listed 'Best First'.
Re^8: What's most efficient way to get list context? (count)
by Roy Johnson (Monsignor) on Apr 15, 2005 at 16:45 UTC
    A slice in a scalar context returns the last element, but could have been made to invoke nethack again.
    Yes, it could have, but it wasn't, and so the concept of multi-context LISTing is reinforced. My point is that There Is More Than One Way To Think About It, and unless there is some behavior that breaks the mental model, there's nothing wrong with the concept of a list in a scalar context. It explains WLM more simply than a whole bunch of special cases that we pretend are absolutely unrelated. They are related by Larry's vision, which appears to include the notion of a LIST.

    The comma is a LIST-construction operator that works in either context, and the slice is another. qw is another. The range operator is not, because in scalar context, it's a completely different operator.


    Caution: Contents may have been coded under pressure.