# 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
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
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_
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
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
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
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
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
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
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
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
11 matches
Mail list logo
