Allison Randal wrote:
James E Keenan wrote:
Everything was smoldering fine up through r41777, where I broke for
the night. But when I came back the next day and 'svn up', I found
that 'make smolder_coretest' would no longer complete.
Status update on pcc_reapply branch on Linux/i386 at r41
On Thu, 2009-10-08 at 23:50 -0700, chromatic wrote:
> On Thursday 08 October 2009 23:46:47 Christoph Otto wrote:
>
> > I guess it kinda makes sense to initialize the complex types (STRING and
> > PMC) and leave garbage in the primitive types (Integer and Float), but it
> > strikes me a premature o
From: chromatic
Date: Thu, 8 Oct 2009 23:50:17 -0700
On Thursday 08 October 2009 23:46:47 Christoph Otto wrote:
> I guess it kinda makes sense to initialize the complex types (STRING and
> PMC) and leave garbage in the primitive types (Integer and Float), but it
> strikes me a
On 10/8/2009 10:45 PM, Martin Kealey wrote:
And thus began a debate: some hold that it's only a "low level buffer" and
that initialization isn't guaranteed; others (like me) hold that this breaks
a fairly fundamental guarantee.
The claim that it's "low level" and therefore it should be "uninitia
Howdy,
Funny y'all should ask about these things, since there is a TT patch
awaiting review for this exact thing.
https://trac.parrot.org/parrot/ticket/1089
kurahaupo++ has a patch there which initializes ResizeableIntegerArray's .
Duke
On Thu, Oct 8, 2009 at 11:50 PM, chromatic wrote:
> O
I've heard a pretty sizable number of complaints recently regarding
the various *Array types, their behaviors and their implementations. I
think it may be worthwhile for us to start thinking about what
behaviors, exactly, these types are intended to provide. It would also
be a very good idea to sta
hi,
PIRC (like IMCC) generates signatures of ops based on the arguments.
Arguments can be among others keyed thingies, such as:
$P0 = new ["Packfile"]
PIRC currently generates new_p_ksc for the above, which is incorrect.
It should be new_p_pc.
My question (and I'm asking this here on the list ju
Hi all,
A few months ago I started adding bits of documentation on PIRC on the wiki:
https://trac.parrot.org/parrot/wiki/PIRCDevelopment
With the recent mentioning of an increased interest in PIRC by
Whiteknight, I felt I should provide some support.
However, most C functions in PIRC have some d
