FWIW, this test passed for me on Linux at the same SVN revision. And it
has always passed for me on Darwin previously, most recently at r31503
on 20080929.
Hope this additional diagnostic info helps:
$ perl t/harness --verbosity=1 t/00-parrot/06-op-inplace.t
t/00-parrot/06-op-inplace
1..11
ok 1
ok 2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 1
ok 9
ok 7
ok 11
All 11 subtests passed
Test Summary Report
---
t/00-parrot/06-op-inplace (Wstat: 0 T
On Sun Oct 05 16:53:10 2008, [EMAIL PROTECTED] wrote:
> I don't often build Rakudo, so I'm not even sure whether this is the
> correct place to report this bug. In any event, this was run on
> Linux at r31685.
>
> make && make test
>
FWIW, the error was reproduced when I typed:
make perl6
Patrick R. Michaud via RT wrote:
On Thu, Sep 25, 2008 at 05:05:16AM -0700, Vasily Chekalkin via RT wrote:
This bug caused by "runops_args" which doesn't populcate
interp->current_args which used in "mmd_arg_tuple_func" to calculate
signature for MMD.
chromatic has suggested that we should wait
Updated information: we added recently a workaround to the utf8 downcase
function, by moving code already present out of the ICU #if block.
This workaround delegates to the ascii downcase when the string has only
codepoints in the ascii range (the way used to do that check is
debatable, must be re
Done in r31684 after MMD changes, adding the test from the previous patch.
On Sun, Oct 05, 2008 at 10:43:45AM -0500, Patrick R. Michaud wrote:
> We seem to have lost the svn-commit mail updates, I haven't seen
> a svn-commit message since r31606 on October 3 (parrot is
> currently at r31676).
>
> Any chance we get could this back? For me it's much easier to
> review
Author: allison
Date: Sun Oct 5 04:30:01 2008
New Revision: 31668
Modified:
trunk/docs/pdds/pdd27_multiple_dispatch.pod
Changes in other areas also in this revision:
Added:
trunk/docs/multidispatch.pod
- copied unchanged from r31667, /branches/pdd27mmd/docs/multidispatch.pod
trunk
NotFound wrote:
But if you talk about perl6, this is not applicable, the perl6
function can have any wanted signature, it will never call the
function directly, it emits the opcode that will call it and can
insert any check or change of his argument. If the sub implementation
allows accidental si
>> But a fake signature makes errors harder to find and can make
>> optimized builds works different as normal ones.
>
> I'm not sure how the signature is "fake". An unsigned integer is a
> subset of integer. Parrot doesn't have a set of $U registers for
> unsigned ints, does it? I suppose the ro
On Sun, Oct 5, 2008 at 10:10 AM, NotFound <[EMAIL PROTECTED]> wrote:
> But a fake signature makes errors harder to find and can make
> optimized builds works different as normal ones.
I'm not sure how the signature is "fake". An unsigned integer is a
subset of integer. Parrot doesn't have a set
We seem to have lost the svn-commit mail updates, I haven't seen
a svn-commit message since r31606 on October 3 (parrot is
currently at r31676).
Any chance we get could this back? For me it's much easier to
review commits and patches arriving by email than to have to
go manually look them up via
> I'd say the fact that it has to do checking within the routine anyway
> is no reason not to add checks to catch errors earlier. Making the
> signature programmer-friendlier is like adding javascript validation
> to a web form - sure, the target of the submission still has to do its
> own validat
I'd say the fact that it has to do checking within the routine anyway
is no reason not to add checks to catch errors earlier. Making the
signature programmer-friendlier is like adding javascript validation
to a web form - sure, the target of the submission still has to do its
own validation, but i
> (I'm making as many parameters and struct members unsigned as possible so that
> the compiler can warn us if we ever use signed values with them. This is one
> nice way to check some of our assumptions.)
But sting_substr is called directly from opcodes, then the simpler way
is that his argument
15 matches
Mail list logo
