[perl #127864] Strange MAIN positional string interpolations

2016-04-09 Thread Pepe Schwarz via RT
>S19 specifies s/specifies/speculated/ ... :)

[perl #127864] Strange MAIN positional string interpolations

2016-04-09 Thread Pepe Schwarz via RT
On Fri Apr 08 19:39:49 2016, madcap.russo...@gmail.com wrote: > From IRC: > 9:22 PM if I pass a : at the beginning of a string > argument to MAIN, it fails to match any signatures and triggers the > Usage message > 9:25 PM MadcapJake, can't reproduce. What's the sig for > MAIN you're using and

[perl #127916] [BUG] Inaccurate assignment to $!shortname in cases where a mixin happens during BUILD time.

2016-04-24 Thread Pepe Schwarz via RT
On Wed Apr 20 02:54:29 2016, jn...@jnthn.net wrote: > On Sun Apr 17 16:34:02 2016, pesc...@gmail.com wrote: > > Consider the following snippet: > > > > 23:28 < psch> m: role Bar::Foo { }; class A { submethod BUILD { self > > does Bar::Foo } }; A.new.WHAT.say > > 23:28 <+camelia> rakudo-moar

[perl #127988] [BUG] Lack of space after != operator changes behaviour

2016-04-25 Thread Pepe Schwarz via RT
On Mon Apr 25 09:20:43 2016, c...@zoffix.com wrote: > > If the programmer omits the space after the != (not equal, numeral) > operator, the behavior of the operator changes to: [assign RHS to LHS, > return !RHS], as can be seen from these examples: > > m: say 0 != 0 > rakudo-moar f05c77:

[perl #124628] [JVM] doesn't know about signals

2016-04-30 Thread Pepe Schwarz via RT
NQP commit d54d719311 and Rakudo commit 1acf805b6 add a workaround for the lack of actual signal handling on the JVM. Note this is for now limited to SIGINT and SIGKILL, and cannot work for any signal that doesn't want the receiving process to exit.

[perl #127949] [JVM] Dying test in S02-literals/allomorphic.t when comparing ComplexStr with infix:

2016-05-01 Thread Pepe Schwarz via RT
On Sun May 01 08:04:06 2016, pesc...@gmail.com wrote: > On Thu Apr 21 12:34:10 2016, barto...@gmx.de wrote: > > On Thu Apr 21 11:53:14 2016, barto...@gmx.de wrote: > > > > > > $ perl6-j -e 'say < 8+9i >.re' > > > Attribute '$!re' is not a native num > > > in block at -e line 1 > > > > Oh, looks

[perl #127949] [JVM] Dying test in S02-literals/allomorphic.t when comparing ComplexStr with infix:

2016-05-01 Thread Pepe Schwarz via RT
On Thu Apr 21 12:34:10 2016, barto...@gmx.de wrote: > On Thu Apr 21 11:53:14 2016, barto...@gmx.de wrote: > > > > $ perl6-j -e 'say < 8+9i >.re' > > Attribute '$!re' is not a native num > > in block at -e line 1 > > Oh, looks like rakudo-j has other problems with the attributes of >

[perl #126713] [BUG] Literal array interpolation in regex doesn't match as expected.

2016-07-11 Thread Pepe Schwarz via RT
On Sat Dec 19 19:44:53 2015, pesc...@gmail.com wrote: > On Mon Nov 23 03:52:55 2015, pesc...@gmail.com wrote: > > Consider the following two regexen and their matching output, or lack > > thereof: > > > > 11:39 < psch> m: say "abcd" ~~ /^(a | b | bc | cd)*?$/; my @a = < a b > > bc cd >; say "abcd"

[perl #129909] [BUG] cannot compile to jar files for client use using --target=jvm

2016-10-19 Thread Pepe Schwarz via RT
On Tue Oct 18 18:07:05 2016, data...@gmail.com wrote: > perl6 --target=jvm --ll-exception --output=guess.jar guess.p6 > > > java.lang.NullPointerException > > in command_eval (gen/jvm/stage2/NQPHLL.nqp:1217) > > in command_eval (src/Perl6/Compiler.nqp:27) > > in command_line

[perl #132104] [JVM] EvalServer leaks threads and memory when using Proc::Async

2018-01-25 Thread Pepe Schwarz via RT
On Thu, 12 Oct 2017 13:35:27 -0700, barto...@gmx.de wrote: > On Sat, 23 Sep 2017 12:28:53 -0700, barto...@gmx.de wrote: > > 3) Feeding the EvalServer with a program that calls 'run' (or > > Proc::Async directly) does heavily leak memory, threads and what not > > (again assuming a clean EvalServer

[perl #132104] [JVM] EvalServer leaks threads and memory when using Proc::Async

2018-01-25 Thread Pepe Schwarz via RT
On Thu, 12 Oct 2017 13:35:27 -0700, barto...@gmx.de wrote: > On Sat, 23 Sep 2017 12:28:53 -0700, barto...@gmx.de wrote: > > 3) Feeding the EvalServer with a program that calls 'run' (or > > Proc::Async directly) does heavily leak memory, threads and what not > > (again assuming a clean EvalServer

[perl #130532] [JVM] Failing tests for itemization of arguments with infix: after introduction of Rakudo::Internals.OneValueIterator

2018-01-29 Thread Pepe Schwarz via RT
On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote: > On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote: > > I managed to golf this a bit: > > > > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () { > > $!foo > > := nqp::null; say nqp::isnull($!foo) ?? "null" !! $!foo }

[perl #130532] [JVM] Failing tests for itemization of arguments with infix: after introduction of Rakudo::Internals.OneValueIterator

2018-01-29 Thread Pepe Schwarz via RT
On Sat, 14 Jan 2017 13:46:47 -0800, barto...@gmx.de wrote: > On Tue, 10 Jan 2017 12:46:48 -0800, barto...@gmx.de wrote: > > I managed to golf this a bit: > > > > $ ./perl6-j -e 'use nqp; class A { has Mu $!foo; method bar () { > > $!foo > > := nqp::null; say nqp::isnull($!foo) ?? "null" !! $!foo }

[perl #126702] [JVM] failing test in S06-multi/subsignature.t: wrong multi candidate called when slurpy and named are passed

2018-01-27 Thread Pepe Schwarz via RT
On Sat, 21 Nov 2015 06:12:07 -0800, barto...@gmx.de wrote: > The following code does not give the expected result ('2') on > rakudo.jvm: > > $ perl6-j -e 'multi catch(| (*@all ) ) { 1 }; multi catch(| (*@all, > :$really! ) ) { 2 }; say catch(0, 5, :!really)' > 1 Neither the mentioned test file