Re: New Perl rewrite - embedded Perl

2000-09-10 Thread Dan Sugalski
At 09:40 PM 9/9/00 +0100, Matthew Gillman wrote: >Basically, my comment is that a lot of commercial applications seem to be >mixing and matching languages together (like C++ and Perl), so it would be >really great if the issues such as Purify errors for embedded Perl were >addressed (I realise

Re: RFCs for thread models

2000-09-10 Thread Dan Sugalski
At 10:26 PM 9/9/00 -0400, Steven W McDougall wrote: >RFC 178 proposes a shared data model for Perl6 threads. In a shared >data model >- globals are shared unless localized >- file-scoped lexicals are shared unless the thread recompiles the > file >- block scoped lexicals may be shared by > - p

Re: A tentative list of vtable functions

2000-09-10 Thread Dan Sugalski
At 07:58 PM 9/9/00 +, Nick Ing-Simmons wrote: >Ken Fox <[EMAIL PROTECTED]> writes: > >Short > >circuiting should not be customizable by each type for example. > >We are already having that argument^Wdiscussion elsewhere ;-) > >But I agree variable vtables are not the place for that. As do I,

Re: RFC 178 (v2) Lightweight Threads

2000-09-10 Thread Dan Sugalski
At 09:43 PM 9/9/00 -0400, Chaim Frenkel wrote: > > "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes: > >DS> Right, but databases are all dealing with mainly disk access. A 1ms lock >DS> operation's no big deal when it takes 100ms to fetch the data being >locked. >DS> A 1ms lock operation *is*

Re: RFC 178 (v2) Lightweight Threads

2000-09-10 Thread Alan Burlison
Chaim Frenkel wrote: > Please elaborate. How deep do you go? $h{a}{b}{c}{d}{e}{f} This is my last mail on this subject - it is a half-assed idea, and this whole thread is becoming too tedious for words. Actually, I'd extend that to the whole p6 process. In fact I think I'll just unsubscribe.

Re: RFCs for thread models

2000-09-10 Thread Benjamin Stuhl
--- Chaim Frenkel <[EMAIL PROTECTED]> wrote: > > "SWM" == Steven W McDougall <[EMAIL PROTECTED]> > writes: > > SWM> If you actually compile a Perl program, like > > SWM> $a = $b > > SWM> and then look at the op tree, you won't find the > symbol "$b", or "b" > SWM> anywhere in it. The

one question about vtbls

2000-09-10 Thread Benjamin Stuhl
I have one question about vtbls that I have not been able to figure out an answer to: How does using a vtbl get rid of the switch(sv->sv_flags) with multi-valued scalars running around? That is, how does one write a vtbl function that can cope with the perl6 equivalent of perl5's sv_setiv(s

Re: RFCs for thread models

2000-09-10 Thread Chaim Frenkel
> "BS" == Benjamin Stuhl <[EMAIL PROTECTED]> writes: >> Now where >> sub recursive() { my $a :shared; ; return >> recursive() } >> would put $a or even which $a is meant, is left as an >> excersize >> for someone brighter than me. BS> %P6-E-MEANINGLESS, "my $a : shared" is a meaningless

Re: one question about vtbls

2000-09-10 Thread Chaim Frenkel
> "BS" == Benjamin Stuhl <[EMAIL PROTECTED]> writes: BS> I have one question about vtbls that I have not been able BS> to figure out an answer to: BS> How does using a vtbl get rid of the switch(sv->sv_flags) BS> with multi-valued scalars running around? That is, how does BS> one write a v

Re: RFC 127 (v1) Sane resolution to large function returns

2000-09-10 Thread Glenn Linderman
Chaim Frenkel wrote: > > "GL" == Glenn Linderman <[EMAIL PROTECTED]> writes: > > GL> Chaim Frenkel wrote: > >> ($foo, $baz, @bar) = (1,(2,3),4) # $foo = 1 $baz=2, @bar=(3,4) > >> > >> Actually, looking at it like that makes it an ugly situation. The 'new' > >> expectation would be to have it