# New Ticket Created by "Paco Linux"
# Please include the string: [perl #59442]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=59442 >
as r31402 : Expanded float precision to 15 digits from 6. One side effect
is that float
Paco Linux (via RT) wrote:
> as r31402 : Expanded float precision to 15 digits from 6. One side effect
> is that float output no longer always has six digits after the dot; this
> drops trailing zeroes. Now the result is correct.
>
> t/benchmark/benchmarks..1/37
> # Failed test 'examples/be
Parrot Bug Summary
http://rt.perl.org/rt3/NoAuth/parrot/Overview.html
Generated at Mon Sep 29 13:00:03 2008 GMT
---
* Numbers
* New Issues
* Overview of Open Issues
* Ticket Status By Version
* Requestors with m
Patrick R. Michaud wrote:
> On Sat, Sep 27, 2008 at 12:18:21AM -0700, Vasily Chekalkin wrote:
>> Hello.
>>
>> There is implementation of Pair.pairs. +3 passed tests in "S29-hash/pairs.t"
>>
>> +$P0 = get_hll_namespace ['Perl6Pair']
>> +'!EXPORT'('pairs', $P0)
>
> It's probably wrong to e
Hi all,
I've given the perl6 wiki 'november'
(http://github.com/viklund/november/tree/master) a go out of
curiosity, and being surprised at the run times (page 35 of
http://viklund.pp.se/november.pdf) have done some profiling using
valgrind.
For the test case all I've been using is running test_w
On Mon, Sep 29, 2008 at 12:15 PM, Nick Glencross
<[EMAIL PROTECTED]> wrote:
> * Most of the GCs are happening in run_thaw to overcome a problem
> with hashes (1938 of the 2024 calls). I tried disabling the forced
> check, but it segfaults indicating that the problem is still there.
> Fixing this G
On Mon, Sep 29, 2008 at 05:32:23PM +0200, Moritz Lenz wrote:
> Patrick R. Michaud wrote:
> > On Sat, Sep 27, 2008 at 12:18:21AM -0700, Vasily Chekalkin wrote:
> >> +$P0 = get_hll_namespace ['Perl6Pair']
> >> +'!EXPORT'('pairs', $P0)
> >
> > It's probably wrong to export 'pairs' here -- the
All,
I've had a go at improving the hash thawing, and while it's not
perfect (it fails on certain cases), I've managed to run november with
the changes.
Unfortunately since the large number of thaws happened early in the
run (when the PMCs in the packfiles are extracted) there aren't many
objects
> It turns out that the namespace was a red herring. The real problem is
> that when iterating over a hash, you cannot assign to a PMC register; it
> must be a string register. So if the base collection is a hash, this
> segfaults:
>
> $P0 = shift iterator
>
> But this works fine:
>
>
# New Ticket Created by Chris Fields
# Please include the string: [perl #59446]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=59446 >
Attached is a patch which implements preliminary support for Regexes
and Closures and
# New Ticket Created by Chris Fields
# Please include the string: [perl #59448]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=59448 >
Attached is a patch which implements preliminary support for Regexes
and Closures and
On Sat Sep 20 04:13:08 2008, masak wrote:
> In Parrot r31286:
>
> $ perl t/examples/library.t
> 1..4
> ok 1 - examples/library/getopt_demo.pir
> ok 2 - examples/library/md5sum.pir
> 7.7
> Failed to load libpcre
> current instr.: 'parrot;PCRE;init' pc 110 (library/pcre.pir:111)
> called from Sub 'p
On Mon, Sep 29, 2008 at 9:36 PM, Kealey, Martin, ihug-NZ
<[EMAIL PROTECTED]> wrote:
> Hmmm, my understanding was that it stopped *splitting* after the limit, but
> it doesn't stop "consuming" the source;
D'oh, you are of course correct; that is in fact the chief utility of
the limit parameter, an
I didn't see anything in the issue tracker, nor did any tests fail,
but am I correct in assuming that array slicing is simply not
implemented yet in Rakudo?
$ ./perl6 -e 'my @a = (1,2,3); say @a[0 .. 1];'
3
it takes the range in item context, which is the size of the range,
and uses that as an in
Carl Mäsak wrote:
> Do not combine 'ne' and '|', like this:
>
> die "Unrecognized directive: TMPL_$directive"
>if $directive ne 'VAR' | 'LOOP' | 'IF';
> One is tempted to assume that this means the same as "$directive ne
> 'VAR' || $directive ne 'LOOP' || $directive ne 'IF"", but it doesn't.
Igor wrote:
Hi Christoph,
I send you the patch attached.
Sincerely,
Igor
Hi Igor,
Thanks again for taking the time to contribute.
Here are some pointers:
First, you're trying too hard. I'm sorry to tell you that after you've spent
so much effort, but this change should be fairly minimal.
16 matches
Mail list logo