Tom Christiansen writes:
: It would appear that altering &&/|| on LHS context would entail,
: in the list assignment scenario, calling that operand in list context
: and then deciding whether it were true or not by some "intuitive"
: means (almost certainly by using whether its element count were
: zero or non-zero). You'd have to squirrel away those list values
: first to avoid re-evaluation, but this does not seem unduly onerous.
If a lazy list object were returned, it could even specify its own
boolean meaning. Conventionally it would have the same meaning
as array currently has in a boolean context, but one can imagine
funny array types that pick their own meanings for:
@a->bool
@a->len
@a->num
@a->str
...
Larry
