Re: RFC 178 (v1) Lightweight Threads by Ken Fox- September 8, 2000 Steven W McDougall wrote:> Question: Can the interpreter determine when a variable becomes> shared> > Answer: No. Then neglecting to put a :shared attribute on a shared> variable will crash the interpreter. This doesn&39;t seem very Perlish.If the variable isn&39;t :shared then how can it be shared! In otherwords, if it&39;s not :shared, you&39;re going to get a copy of the variablefor each thread. AFAIK, the only places where this is visible areglobal variables and closures....http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg313.html Re: RFC 178 (v1) Lightweight Threads by Ken Fox- September 8, 2000 Steven W McDougall wrote:> How do our&39; and my&39; control mutex lockingI was assuming that all global (or "non-my" rather) variables would bydefault be shared when using a thread-enabled perl. That seems like asensible default. If we&39;re going to require the :shared modifier, thenignore my comments on "our" vs. "my".Regardless, it seems that perl must make a copy of a closure&39;senvironment for each thread the closure runs under. If a variable in...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg312.html RFC 178 (v3) Lightweight Threads by Perl6 RFC Librarian- September 7, 2000 This and other RFCs are available on the web at http:dev.perl.orgrfc=head1 TITLELightweight Threads=head1 VERSION Maintainer: Steven McDougall <swmcdworld.std.com> Date: 30 Aug 2000 Last Modified: 7 Sep 2000 Mailing List: perl6-language-flowperl.org Number: 178 Version: 3 Status: Developing=head1 ABSTRACTA lightweight thread model for Perl.=over 4=item All threads see the same compiled subroutines=item All threads share the same global variables=item Threads can create...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg311.html RFC 185 (v2) Thread Programming Model by Perl6 RFC Librarian- September 6, 2000 This and other RFCs are available on the web at http:dev.perl.orgrfc=head1 TITLEThread Programming Model=head1 VERSION Maintainer: Steven McDougall <swmcdworld.std.com> Date: 31 Aug 2000 Last Modified: 05 Sep 2000 Mailing List: perl6-language-flowperl.org Version: 2 Number: 185 Status: Developing=head1 ABSTRACTThis RFC describes the programming interface to Perl6 threads. It documents the function calls, operators, classes, methods, orwhatever else the language provides for...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg310.html Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go by Chaim Frenkel- September 5, 2000 >>>>> "PS" == Peter Scott <PeterPSDT.com> writes:PS> I find myself wishing there were something we could do about thePS> context rules. They seem simple enough, individually, but whenPS> you put them together - well, there was a quiz a year or so ago -PS> I forget whether it was in TPJ or Usenet - where someone posted 10PS> or so code fragments and challenged readers to figure out whatPS> they did. And they were all very simple things on the...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg309.html Re: The distinction between "do BLOCK while COND" and "EXPRwhile COND" should go by Peter Scott- September 5, 2000 At 01:20 PM 9300 +1100, Damian Conway wrote:> > Modulo some superpositional silliness,>>Hey! I resemble that remark!>>DamianI guess this means we should expect a N&39;Yuk module some time in the future...--Peter ScottPacific Systems Design Technologieshttp://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg308.html Re: The distinction between "do BLOCK while COND" and "EXPRwhile COND" should go by Nathan Torkington- September 5, 2000 Peter Scott writes:> Hey, waitaminute. That isn&39;t a list in sub fn in the first place; it&39;s > three expressions separated by scalar commas. Why is there no complaint > about useless use of a constant in void context> > $ perl -Mstrict -wle &39;sub freturn(3,5,7) my $x = f()&39;> $ perl -Mstrict -wle &39;my $x = (3,5,7)&39;> Useless use of a constant in void context at -e line 1.> Useless use of a constant in void context at -e line 1.> $> > If context...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg306.html Re: The distinction between "do BLOCK while COND" and "EXPR while COND" should go by Tom Christiansen- September 5, 2000 >Hey, waitaminute. That isn&39;t a list in sub fn in the first place; it&39;s >three expressions separated by scalar commas. Why is there no complaint >about useless use of a constant in void context>$ perl -Mstrict -wle &39;sub freturn(3,5,7) my $x = f()&39;>$ perl -Mstrict -wle &39;my $x = (3,5,7)&39;>Useless use of a constant in void context at -e line 1.>Useless use of a constant in void context at -e line 1.>$>If context propagates through subroutine calls why..http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg307.html Re: The distinction between "do BLOCK while COND" and "EXPRwhile COND" should go by Peter Scott- September 5, 2000 At 01:45 PM 9400 -0600, Tom Christiansen wrote:> >package main;> >sub fn return (3, 5, 7) > >tie $x, &39;MaiTai&39;;> >$x = fn;> >$ tmpfoo> >STORE: 7>> >Why don&39;t I see three STOREs>>Because Perl is too clever to bother. :-)Hey, waitaminute. That isn&39;t a list in sub fn in the first place; it&39;s three expressions separated by scalar commas. Why is there no complaint about useless use of a constant in void context$ perl -Mstrict -wle...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg305.html Re: RFC 178 (v2) Lightweight Threads by Chaim Frenkel- September 4, 2000 >>>>> "PRL" == Perl6 RFC Librarian <perl6-rfcperl.org> writes:PRL> All threads see the same compiled subroutinesWhy Why not allow two different threads to have a different view ofthe universePRL> All threads share the same global variables_All_ or only as requested by the user (ala :shared)PRL> Threads can create thread-local storage by C<local>izing global variablesI&39;d prefer the other way. Sharing has to be declared. Much less work onthe...http://www.nntp.perl.org/group/perl.perl6.language.flow/2000/09/msg304.html |