Re: Master-Apprentice and a "sneak peek"

2001-05-24 Thread Dave Mitchell
A. C. Yardley" <[EMAIL PROTECTED]> wrote: >How about you take sv.c? And I'll take av.c and hv.c? Sound good? okay, its a deal! Simon Cozens <[EMAIL PROTECTED]> wrote: > ACY's taking a look into this too, so you may want to co-ordinate to avoid > clashing. I've also told him what I'd like: some

Re: Stacks & registers

2001-05-24 Thread Nick Ing-Simmons
Uri Guttman <[EMAIL PROTECTED]> writes: >> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes: > > NI> "We" need to decide where a perl6 sub's local variables are going > NI> to live (in the recursive case) - if we need a "stack" anyway it > NI> may make sense for VM to have ways of indexi

Re: Stacks & registers

2001-05-24 Thread Nick Ing-Simmons
Alan Burlison <[EMAIL PROTECTED]> writes: >> 1. When you call deep enough to fall off the end of the large register >>file an expensive "system call" is needed to save some registers >>at the other end to memory and "wrap", and then again when you >>come "back" to the now-in-memory reg

Re: Perl, the new generation

2001-05-24 Thread Mike Lacey
Michael, Thank you for your reply, my apologies for taking so long to reply - I have been away on a course. You make a good point concerning the Llama book. I'm sorry that my email irritated you; it was not intended to do so. Regards, Mike - Original Message - From: "Michael G Schwer

Re: Stacks & registers

2001-05-24 Thread Uri Guttman
> "NI" == Nick Ing-Simmons <[EMAIL PROTECTED]> writes: NI> Uri Guttman <[EMAIL PROTECTED]> writes: >> but indexing directly into a stack frame is effectively a register >> window. the problem is that you need to do an indirection through the >> window base for every access and that i

Re: Master-Apprentice and a "sneak peek"

2001-05-24 Thread Simon Cozens
On Thu, May 24, 2001 at 03:12:03PM +0100, Dave Mitchell wrote: > Are you also interested in functions on scalars that happen to be in pp*.c > rather than sv.c? Definitely; I want an idea of what Perl 5 expects to be able to do with scalars and aggregates so that I know what Perl 6 ought to expect

slices

2001-05-24 Thread Raul Miller
Caution: I'm not yet up to speed on everything perl6. However, I've dealt with stuff like slices in a variety of non-perl contexts, and maybe I'll propose some questions which no one has brought up, yet. First: @a[@(...)] looks plausible as a slice syntax. Or -- if you specify an array value as

Re: slices

2001-05-24 Thread James Mastros
From: "Raul Miller" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 24, 2001 7:49 PM Subject: slices > First: @a[@(...)] looks plausible as a slice syntax. Or -- if you > specify an array value as an index, shouldn't that be a slice? I like your second choice better. That is to s

Re: slices

2001-05-24 Thread Raul Miller
First off, sorry about the noise -- I expect that Larry will have this mostly worked out already. [And, when I re-read Apocalypse 2, I saw that I had almost literally stolen some of his sentences. *blush*] On Thu, May 24, 2001 at 10:19:12PM -0400, James Mastros wrote: > But what about: @foo[(1,2

re: properties

2001-05-24 Thread Damian Conway
MJD just pointed out a minor thinko in the explanatory Perl6 code I posted: sub gorkulator { ... return $result is true if defined $result; return undef is Because($borked); } # and later... if ($res = gorkulator) {