[perl #77660] [BUG] X*= doesn't modify the original array in Rakudo

2010-09-02 Thread Carl Mäsak
# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #77660] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=77660 > rakudo: my @a = 1, 2, 3; @a X*= 5; say @a.perl; @a = @a X* 5; say @a.perl; rakudo 33e9

Re: Pragma to change presentation of numbers in Perl 6.

2010-09-02 Thread Dave Whipp
Matthew wrote: use base 16; my $a = 10; say $a; puts the number 0x10 into $a, and outputs `10'. Here, say $a.fmt('%d') would output `16'. As someone who has implemented, and used, mini-languages with such a feature, I'd say that the confusion that it would cause does significantly outweigh

Re: [perl #77644] memory leak on eval

2010-09-02 Thread Patrick R. Michaud
On Thu, Sep 02, 2010 at 11:20:52AM -0400, Will Coleda wrote: > > Currently each eval() execution results in compiling and > > loading at least two additional Parrot subs into memory > > that represent the eval'ed code.  As far as I can tell, > > once loaded there's currently no way for a Parrot Sub

Re: [perl #77644] memory leak on eval

2010-09-02 Thread Will Coleda
On Thu, Sep 2, 2010 at 10:35 AM, Patrick R. Michaud wrote: > On Thu, Sep 02, 2010 at 03:02:43AM -0700, Paweł Pabian wrote: >> Star 2010.08 release >> >> Run folloing code and it will start eating up memory quite fast. >> >> $ perl6 -e 'use Test; eval_lives_ok "" for 1..1' >> >> [11:59] eval '

Re: [perl #77644] memory leak on eval

2010-09-02 Thread Patrick R. Michaud
On Thu, Sep 02, 2010 at 03:02:43AM -0700, Paweł Pabian wrote: > Star 2010.08 release > > Run folloing code and it will start eating up memory quite fast. > > $ perl6 -e 'use Test; eval_lives_ok "" for 1..1' > > [11:59] eval '' while 1; also leaks > [11:59] so I think it's eval() that leaks

[perl #77646] [BUG] executing the same eval twice without an enclosing block

2010-09-02 Thread via RT
# New Ticket Created by Nuno Carvalho # Please include the string: [perl #77646] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=77646 > IRC log: 11:07 < smash> rakudo: eval "say 1" for 1..4; 11:07 <+p6eval> rakudo 27d54d:

[perl #77650] Test.pm - eval_lives_ok emits warning "Use of uninitialized value in numeric context"

2010-09-02 Thread via RT
# New Ticket Created by Paweł Pabian # Please include the string: [perl #77650] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=77650 > [12:21] rakudo: use Test; eval_lives_ok '1<&1' [12:21] rakudo 27d54d: OUTPUT«Use of un

[perl #77648] Test.pm - warn cause eval_lives_ok test to fail

2010-09-02 Thread via RT
# New Ticket Created by Paweł Pabian # Please include the string: [perl #77648] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=77648 > .08 Star release Warn does not interrupt code execution: $ perl6 -e 'warn "foo"; say "

[perl #77644] memory leak on eval

2010-09-02 Thread via RT
# New Ticket Created by Paweł Pabian # Please include the string: [perl #77644] # in the subject line of all future correspondence about this issue. # http://rt.perl.org/rt3/Ticket/Display.html?id=77644 > Star 2010.08 release Run folloing code and it will start eating up memory quite fast.