Being generally in favor of moving quickly toward a 1.0 release, I'm
looking at this from the perspective of "what's essential and what's not
essential"?
Allison Randal wrote:
I'd like to do away with the PMC_DATA_IN_EXT flag so the "DPOINTER
*data;" struct element is always in the PMC struc
Am Mittwoch, 23. Mai 2007 04:05 schrieb Patrick R. Michaud:
> Here's the perl 6 code:
>
> my $a = sub { ... }; # $a is a subroutine reference
> my $b := $a;
> # ...;
> $a = 4; # $a is now an Int
>
> How to do the above in PIR if we can't morph a Sub?
I may be
On Tue, May 22, 2007 at 10:32:23PM -0400, Will Coleda wrote:
>
> On May 22, 2007, at 10:05 PM, Patrick R. Michaud wrote:
>
> >And I'm really
> >not sure how to create a Perl6Sub from PIR source code.
>
> We're already doing this in tcl.
>
> See src/class/tclproc.pir for the PIR class which has
On May 22, 2007, at 10:05 PM, Patrick R. Michaud wrote:
And I'm really
not sure how to create a Perl6Sub from PIR source code.
We're already doing this in tcl.
See src/class/tclproc.pir for the PIR class which has Sub for a
parent class.
runtime/builtin/proc.pir then puts this to use:
On Tue, May 22, 2007 at 04:42:15PM -0700, Allison Randal wrote:
> Patrick R. Michaud wrote:
> >
> >Now then, this assumes that every type knows how to morph itself
> >into an .Undef and that .Undef can handle assignment from any type.
> >For many PMC classes this isn't (or hasn't been) the case; fr
On Tue, May 22, 2007 at 01:41:32PM -0700, Allison Randal wrote:
> Oh, could someone capture that IRC discussion we just had and paste it
> on the list?
Here it is (long, 247 lines).
Pm
19:45 I know I should already know this, but is there a way to make
a named function that is global to al
Oh, could someone capture that IRC discussion we just had and paste it
on the list?
Allison
On Tue, May 22, 2007 at 08:20:19AM -0500, Patrick R. Michaud wrote:
> On Tue, May 22, 2007 at 01:25:33PM +0100, Nicholas Clark wrote:
> >
> > And how often does the type of a PMC change, such that its internal
> > data layout changes? In Perl 5 this morphing happens everywhere,
> > but in Parrot
On Tue, May 22, 2007 at 01:25:33PM +0100, Nicholas Clark wrote:
>
> And how often does the type of a PMC change, such that its internal
> data layout changes? In Perl 5 this morphing happens everywhere,
> but in Parrot?
Actually, until/unless we have a "scalar container" or "reference"
PMC of s
On Mon, May 21, 2007 at 06:48:25PM -0700, Allison Randal wrote:
> On variable-sized PMCs, I generally agree with the goals the proposal is
> trying to accomplish, but I want to tackle these goals in a simpler way.
> One of the goals mentioned for the proposal was to shrink down the size
> of PM
10 matches
Mail list logo
