Re: Digest module and Q:PIR blocks

2010-06-06 Thread Patrick R. Michaud
On Sun, Jun 06, 2010 at 11:06:07PM +0200, Cosimo Streppone wrote: > Hi all, > > Just for fun, I'm trying to write a Digest::MD5 module for Rakudo. > Right now I'm stuck with something like: > > sub test (Str $text) { > Q:PIR { > load_bytecode 'Digest/MD5.pbc' > $P0 = f

[perl #73772] [BUG] Rakudo returns the wrong thing from a <> quote with only whitespace in it

2010-06-06 Thread Patrick R. Michaud via RT
Now fixed in 841262f. Assigning to moritz++ for test verification to close ticket. Pm

Digest module and Q:PIR blocks

2010-06-06 Thread Cosimo Streppone
Hi all, Just for fun, I'm trying to write a Digest::MD5 module for Rakudo. Right now I'm stuck with something like: sub test (Str $text) { Q:PIR { load_bytecode 'Digest/MD5.pbc' $P0 = find_lex '$text' $P1 = _md5sum($P0) $S0 = _md5_hex($P1)

[perl #74050] bogus hash vs. block distinction.

2010-06-06 Thread Patrick R. Michaud via RT
Now fixed in 06723b4... assigning to moritz++ for test verification and unfudging. Pm

[perl #74828] [BUG] ^attributes attributes are erroneously sent in triplicate in Rakudo

2010-06-06 Thread jn...@jnthn.net via RT
On Sat May 01 09:30:15 2010, masak wrote: > rakudo: class A { has $.a; has $.b }; A.^attributes>>.name.perl.say > rakudo c4857a: OUTPUT«("\$!a", "\$!b", "\$!a", "\$!b", > "\$!a", "\$!b")␤» > finanalyst: that works. > "works" > :) > have you actually looked at the output? > it's... interestin

[perl #65022] tests available

2010-06-06 Thread kyleha
This is an automatically generated mail to inform you that tests are now available in t/spec/S12-class/basic.t commit 435e1ba16db479c8904ff5d831cabdeb5a20ab79 Author: radus Date: Sun Jun 6 12:44:13 2010 + [t/spec] Added tests for RT 65022 - Nested classes declared inside different cl

[perl #75446] [BUG] The curious case of the one-off line number in Rakudo

2010-06-06 Thread jn...@jnthn.net via RT
On Sun May 30 05:44:14 2010, masak wrote: > I've found a case where a line number is one-off. should I > nopaste it? > masak: please > I don't think it's the fault of the new backtraces thing, to > be honest. > more like a result of parsing or something. > Well, the other thing is that we don'

[perl #75458] package Foo; does not cause parsefail

2010-06-06 Thread jn...@jnthn.net via RT
On Sun May 30 10:21:26 2010, lue wrote: > [10:13:37] rakudo: package Foo; > [10:13:41] rakudo 749fe9: ( no output ) > [10:13:50] lue: care to submit that one? > [10:13:59] * lue submits rakudobug > > This should instead return a parsefail, according to S10. At this time, > even STD believes i

[perl #75514] [BUG] &exit produces a (disappointing) backtrace in Rakudo

2010-06-06 Thread jn...@jnthn.net via RT
On Wed Jun 02 07:57:33 2010, masak wrote: > rakudo: exit > rakudo 18d996: OUTPUT«␤ in main program body at line 1␤» > * masak submits rakudobug > > As far as I understand, &exit, while probably implemented internally > using some exception mechanism or other, shouldn't print a backtrace. > Back

[perl #65514] Can't mix in True or False as ($value but True)

2010-06-06 Thread jn...@jnthn.net via RT
On Sat May 09 04:31:06 2009, moritz wrote: > This works fine: > > $ ./perl6 -e 'enum A ; ("abc" but c).uc.say' > ABC > > This doesn't > > $ >./perl6 -e '("abc" but Bool::True).uc.say' > The but operator can only be used with a role or enum value on the right > hand side > You can now write this

[perl #63068] [TODO] Implement $*PROG

2010-06-06 Thread jn...@jnthn.net via RT
On Fri Feb 06 03:07:30 2009, masak wrote: > the distro-specific 'ps' hack is a *temporary* workaround > for a missing $*PROG special var. > mberends: oh. :) > mberends: did you also create a big fat RT TODO ticket for $*PROG? > for the umpteenth time, sorry, no. > * masak does so I assume this

[perl #67372] [BUG] warn without parameters fails

2010-06-06 Thread jn...@jnthn.net via RT
On Wed Jul 08 19:55:59 2009, s1n wrote: > (21:42:03) s1n: rakudo: warn > (21:42:06) p6eval: rakudo 70bfd5: OUTPUT«Warning! Something's wrong.␤␤» > (21:42:10) s1n: hah > (21:42:25) TimToady: it shouldn't have a newline > (21:42:39) TimToady: Perl 5 would tell you the line number > > This probably s

[perl #75434] tests available

2010-06-06 Thread kyleha
This is an automatically generated mail to inform you that tests are now available in at least one of these files: t/spec/S12-methods/parallel-dispatch.t, t/spec/packages/ContainsUnicode.pm commit 9b5d136c93293e3dd9e66bc7395f1960ee26b229 Author: moritz Date: Sun Jun 6 09:27:54 2010 +