Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

2000-09-04 Thread Piers Cawley
Damian Conway <[EMAIL PROTECTED]> writes: >> Modulo some superpositional silliness, > > Hey! I resemble that remark! And we love you for it. -- Piers

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

2000-09-04 Thread Chaim Frenkel
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes: TC> Oh. You want lists to act like arrays. That's a very big change. Do you have any objection? The intended avoidance of flattening to as late as possible might have that effect. >> You are letting the scalar context of the caller to

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

2000-09-04 Thread Tom Christiansen
>Then please explain why scalar(return (1,2,3)) doesn't do what at first >glance it seems it should. Because X(Y) != Y(X). You should have written "return scalar" if you wanted to return a scalar. >And for the life of me I can't see how > $x=(1,2, (3,4,fn,6) ) >fn ends up in scalar co

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

2000-09-04 Thread Chaim Frenkel
> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes: TC> You will be miserable until you learn the difference between TC> scalar and list context, because certain operators know which TC> context they are in, and return a list in contexts wanting a TC> list, but a scalar val

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

2000-09-04 Thread Peter Scott
At 06:49 AM 9/3/00 -0600, Tom Christiansen wrote: > > sub fn { return (3,5,7) } > > $x = fn;# I want $x==3 > >Why should it return the first one? It returns the last one! >It's just doing what you told it, which was: > > $x = 3; > $x = 5; > $x = 7; It does? What

Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go

2000-09-04 Thread Tom Christiansen
>package main; >sub fn { return (3, 5, 7) } >tie $x, 'MaiTai'; >$x = fn; >$ /tmp/foo >STORE: 7 >Why don't I see three STOREs? Because Perl is too clever to bother. :-) --tom

Re: RFC 178 (v2) Lightweight Threads

2000-09-04 Thread Chaim Frenkel
> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes: PRL> All threads see the same compiled subroutines Why? Why not allow two different threads to have a different view of the universe? PRL> All threads share the same global variables _All_ or only as requested by the user (ala :sha

RFC 178 (v2) Lightweight Threads

2000-09-04 Thread Perl6 RFC Librarian
This and other RFCs are available on the web at http://dev.perl.org/rfc/ =head1 TITLE Lightweight Threads =head1 VERSION Maintainer: Steven McDougall <[EMAIL PROTECTED]> Date: 30 Aug 2000 Last Modified: 02 Sep 2000 Version: 2 Mailing List: [EMAIL PROTECTED] Number: 178 Status: