i found some strange behaviour in perlarray.pmc
Consider this code:
new P0, .PerlArray, 2 # P0[2]
set P0, 2, 1 # P0[2] = 1
set P0, -4, 1 # P0[-4] = 1
# Above runs some strange code:
# ix += SELF->cache.int_val
# where ix is our key
# i
On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> On Mon, Jun 24, 2002 at 05:21:45PM -0400, David J. Goehrig wrote:
> > On Sun, Jun 23, 2002 at 09:50:02PM +0100, Tim Bunce wrote:
> > > Much more likely is some kind of wrapper that manages a simple
> > > perl5-like run-time environme
On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> > Of course, another approach is to embed the existing Perl5 interpreter
> > within the Perl 6 interpreter; Perl6 subs call glue which calls Perl subs
> > which calls perl5
Last night I wanted to see just how much of the API very vanilla
XS code would require. In the limited sampling I did, I found
37 distinct functions and macros. Based on this, I'd say a reasonable
guestimate for minimal core functionality is about 50 distinct functions.
Best guesses would plac
At 9:50 PM +0100 6/23/02, Tim Bunce wrote:
>On Mon, Jun 17, 2002 at 07:59:33PM -0400, David J. Goehrig wrote:
>>
>> qw/ who is praying for parrot to support XS code,
>> cause he doesn't want to rewrite
>> SDL_perl's 11,000 lines /;
>
>I'm sure that's not going to happen.
>
>Much more li
At 1:56 PM +0100 6/20/02, Peter Haworth wrote:
>On Wed, 19 Jun 2002 12:15:57 -0400, Dan Sugalski wrote:
>> At 6:08 PM +0200 6/19/02, Stéphane Payrard wrote:
>> >Should not we think matrices in the light of hyperators?
>>
>> Of course. But the hyper version of the operators all map directly to
>
At 11:11 AM -0600 6/20/02, Luke Palmer wrote:
> > We don't want to accidentally turn that into a hyperplus on @a's PMC, when
>> it should really be a plus on the scalar version of @a.
>
>Which is a reference. You're adding to a reference? You can't do that
>(or does it somehow scalarify to the
At 8:41 AM -0500 6/25/02, Dave Goehrig wrote:
>Last night I wanted to see just how much of the API very vanilla
>XS code would require. In the limited sampling I did, I found
>37 distinct functions and macros. Based on this, I'd say a reasonable
>guestimate for minimal core functionality is abou
And i think it's worth saying that the XS hook should be a well-behaved
parrot extension, once the extension API is defined. Having it get too
intertwined with parrot's guts would be a terrible thing.
--Josh
At 9:42 on 06/25/2002 CDT, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 8:41 AM -05
At 10:53 AM -0400 6/25/02, Josh Wilmes wrote:
>And i think it's worth saying that the XS hook should be a well-behaved
>parrot extension, once the extension API is defined. Having it get too
>intertwined with parrot's guts would be a terrible thing.
Oh, absolutely. The XS interface will be a lay
On Tue, Jun 25, 2002 at 09:42:50AM -0500, Dan Sugalski wrote:
> That'd be cool. Be aware that Parrot, at the moment, has *no*
> extension API at the moment.
Well the bigger problem for the XS compat layer will be the utter
lack of perl5 STASHes and GVs. The namespace games are just going
to ha
On Mon, Jun 24, 2002 at 05:58:23PM -0500, Dan Sugalski wrote:
> At 9:50 PM +0100 6/23/02, Tim Bunce wrote:
> >On Mon, Jun 17, 2002 at 07:59:33PM -0400, David J. Goehrig wrote:
> >>
> >> qw/ who is praying for parrot to support XS code,
> >>cause he doesn't want to rewrite
> >>SDL_perl's 1
On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
> On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> > On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> > > Of course, another approach is to embed the existing Perl5 interpreter
> > > within the Perl 6 interp
At 9:58 AM -0500 6/25/02, Dave Goehrig wrote:
>On Tue, Jun 25, 2002 at 09:42:50AM -0500, Dan Sugalski wrote:
>> That'd be cool. Be aware that Parrot, at the moment, has *no*
>> extension API at the moment.
>
>Well the bigger problem for the XS compat layer will be the utter
>lack of perl5 STASHe
Since we have mutable strings, I added a new routine string_append to
string.c and changed core.ops to use it for the "concat Sx, Sy" case
where x is both a source and destination. This saves rather a lot of
copying in the life benchmark (which I changed a bit to use the new
form in spots) and
On Tue, Jun 25, 2002 at 04:45:37PM +0100, Tim Bunce wrote:
> On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
> > On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> > > On Tue, Jun 25, 2002 at 12:23:34AM +0100, Dave Mitchell wrote:
> > > > Of course, another approach is to
On Tue, Jun 25, 2002 at 05:17:56PM +0100, Dave Mitchell wrote:
> On Tue, Jun 25, 2002 at 04:45:37PM +0100, Tim Bunce wrote:
> > On Tue, Jun 25, 2002 at 11:35:20AM +0100, Dave Mitchell wrote:
> > > On Tue, Jun 25, 2002 at 11:08:53AM +0100, Tim Bunce wrote:
> > > > On Tue, Jun 25, 2002 at 12:23:34AM
On Wed, 19 Jun 2002, Ashley Winters wrote:
> I don't think you need to worry about optimizing complex operations too much,
> the PDL people have come up with miracles before... they just need the tools.
>
Sorry yo come in late but I would hope that the PDL people would not have
to come up wit
18 matches
Mail list logo
