Re: I Don't Understand The Context Allocation/Destruction Code

On Saturday 21 April 2007 22:49, Patrick Rutkowski wrote: > I'm not looking at it for any particular reason. My interest in > helping work on parrot began only yesterday. First I spent last night > reading a few pdds. Then this morning in an effort to familiarize > myself with the implementation d

Re: I Don't Understand The Context Allocation/Destruction Code

On Apr 21, 2007, at 8:24 PM, chromatic wrote: Parrot_alloc_context() performs some calculations about the number of registers used to determine how much memory to allocate: const size_t size_n = sizeof (FLOATVAL) * n_regs_used[REGNO_NUM]; const size_t size_nip = size_n + sizeof

Re: I Don't Understand The Context Allocation/Destruction Code

On Apr 22, 2007, at 12:59 AM, chromatic wrote: On Saturday 21 April 2007 21:26, Patrick Rutkowski wrote: I was just reading (s/reading/trying to read/) the same routine earlier this morning. I'm glad to see that I'm not alone in my confusion. Me too, but I'm now seriously wondering *why* yo

Re: [perl #42408] Re: [PATCH] refactor vtable overriding, delegate.c generation

On Saturday 21 April 2007 18:20, Alek Storm wrote: > This patch has been sitting for over a week. Is there a problem? I > can't continue work in this area until this is committed. It came in just before the release and it touched a lot of files, so I (speaking only for myself) let it sit for a c

Re: I Don't Understand The Context Allocation/Destruction Code

On Saturday 21 April 2007 21:26, Patrick Rutkowski wrote: > I was just reading (s/reading/trying to read/) the same routine > earlier this morning. I'm glad to see that I'm not alone in my > confusion. Me too, but I'm now seriously wondering *why* you were reading it. It's not the lightest, bri

Re: I Don't Understand The Context Allocation/Destruction Code

I was just reading (s/reading/trying to read/) the same routine earlier this morning. I'm glad to see that I'm not alone in my confusion. Is it possible to track down the author of those odd bit-shifting statements in order to ask him about it directly? I would do it myself but I'm still learning

I Don't Understand The Context Allocation/Destruction Code

Parrot_alloc_context() performs some calculations about the number of registers used to determine how much memory to allocate: const size_t size_n = sizeof (FLOATVAL) * n_regs_used[REGNO_NUM]; const size_t size_nip = size_n + sizeof (INTVAL) * n_regs_used[REGNO_INT] + si

Re: [perl #42408] Re: [PATCH] refactor vtable overriding, delegate.c generation

This patch has been sitting for over a week. Is there a problem? I can't continue work in this area until this is committed. -- Alek Storm

Re: [perl #42653] PCCMETHOD failures on freebsd/amd64

On Apr 21, 2007, at 12:41 PM, chromatic wrote: On Saturday 21 April 2007 04:01, Joshua Isom wrote: I'm getting failures in t/pmc/class.t, t/pmc/exporter.t, t/pmc/pccmethod_test.t, t/pmc/role.t, and t/pmc/smop_attribute.t and all seem to be related to PCCMETHOD's. The failures occur in inter_

Re: [perl #42653] PCCMETHOD failures on freebsd/amd64

On Saturday 21 April 2007 04:01, Joshua Isom wrote: > I'm getting failures in t/pmc/class.t, t/pmc/exporter.t, > t/pmc/pccmethod_test.t, t/pmc/role.t, and t/pmc/smop_attribute.t and > all seem to be related to PCCMETHOD's. The failures occur in > inter_call.c, fetch_arg_op(). The macro's of UVal

[perl #42653] PCCMETHOD failures on freebsd/amd64

# New Ticket Created by Joshua Isom # Please include the string: [perl #42653] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=42653 > I'm getting failures in t/pmc/class.t, t/pmc/exporter.t, t/pmc/pccmethod_test.t, t/pmc/r

Weekly Perl 6 mailing list summary for 01-07 April, 2007

This week on the Perl 6 mailing lists "developers shouldn't live in fear of $^O" -- Jerry Gay, in 'Use of English pragma ' Language Second Perl 6 Microgrant - Phil Crow on Java to Perl 6 declaration converter Leon Brocard announced t