[perl #128123] [JVM] failing test in S03-metaops/hyper.t after change from postfix:<++> to prefix:<++>

On Wed May 11 00:51:48 2016, elizabeth wrote: > Doesn’t this imply that prefix ++ on native ints is broken on the JVM. > And thus, a lot of more got broken recently due to my changes?? That was my first thought, too. But this was the only place where rakudo-j got a hickup. Prefix++ works fine in

[perl #126529] [JVM] Buf.pm infix:<~> bug; breaks IO::Socket

This works now (again): $ perl6-j -e 'my Blob $a = "a".encode; my Blob $b = "b".encode; $a ~= $b; say $a.perl' utf8.new(97,98) I added this evaluation as a test to S03-operators/buf.t. I'm closing this ticket as 'resolved'.

[perl #126530] [JVM] Can't concatenate Bufs

On Sat Oct 31 20:31:41 2015, coke wrote: > See S03-operators/buf.t > > Both of these fail: > > ok $a ~ $b eq Buf.new(1, 2, 3, 1, 2, 3, 4), '~ and eq work on bufs'; > is-deeply Buf.new(1, 2, 3) ~ Buf.new(4, 5), Buf.new(1, 2, 3, 4, 5), '~ > concatenates'; These tests pass now (again). I'm closing

Re: [perl #128161] Run time “SORRY!” when the range starts with whatever star (*...‘WAT’)

My guess would be that there’s a string EVAL under the hood somewhere: $ 6 'say "hello"; EVAL "foo"' hello ===SORRY!=== Error while compiling /Users/liz/Github/rakudo.moar/EVAL_0 Undeclared routine: foo used at line 1 Agree that the error could be considered LTA, as the “SORRY” indicates

Re: [perl #128159] [RFC] Disallow Invisible Terms and Operators for Security Reasons

+1 from me. Is there a unicode property that indicates invisibleness? Liz === > On 16 May 2016, at 14:35, Zoffix Znet (via RT) > wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string: [perl #128159] > # in the subject line