>I read your message and agree. Not that I liked the idea that much even >before considering the ramifications. But do you agree that even >seasoned perlers have trouble anticipating how a list/array is going to >be converted to a scalar? A list or array? No, I don't agree. How to predict what an arbitrary function will behave in list context? Sure, that one I'll buy for buck. >I'd vote for no C<list> operator, but for adding a count operator and a >last element operator. I suggest ()= for the first and C<peek> for the >second. Or as Graham shows, "=()=" is the list-counting assignment operator. :-) What's wrong with (...)[-1] for the last element and (...)[0] for the first one? But as I showed, these can surely be nastily inefficient for really big lists. --tom
- Re: RFC 175 (v1) Add C<list> keyword to force list ... Nathan Wiger
- Re: RFC 175 (v1) Add C<list> keyword to force list ... Graham Barr
- Re: RFC 175 (v1) Add C<list> keyword to force list ... Damian Conway
- Re: RFC 175 (v1) Add C<list> keyword to force ... Bart Lateur
- Re: RFC 175 (v1) Add C<list> keyword to fo... Peter Scott
- Re: RFC 175 (v1) Add C<list> keyword to force list ... Damian Conway
- Re: RFC 175 (v1) Add C<list> keyword to force ... Tom Christiansen
- Re: RFC 175 (v1) Add C<list> keyword to fo... Steve Fink
- Re: RFC 175 (v1) Add C<list> keyword t... Graham Barr
- Re: RFC 175 (v1) Add C<list> keyword t... Tom Christiansen
- Re: RFC 175 (v1) Add C<list> keyword to fo... Nathan Wiger
- Re: RFC 175 (v1) Add C<list> keyword t... Tom Christiansen
- Change "($one, $two)=" behavio... Nathan Wiger
- Re: Change "($one, $two)="... Tom Christiansen
- Re: Change "($one, $two)="... Nathan Wiger
- Re: Change "($one, $two)="... Tom Christiansen
- Re: Change "($one, $two)="... Nathan Wiger
- Re: Change "($one, $two)="... Tom Hughes
- Re: Change "($one, $two)="... Jeremy Howard
- Re: Change "($one, $two)="... Damian Conway