[perl6/specs] 9abc8f: [questions] answer Q2 by pmichaud++

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9abc8f20f1fb368054b52b11793618451ba9d629 https://github.com/perl6/specs/commit/9abc8f20f1fb368054b52b11793618451ba9d629 Author: Moritz Lenz Date: 2012-06-29 (Fri, 29 Jun 2012) Changed paths: M questi

[perl #77174] [BUG] "maximum recursion depth exceeded" from: my @a //= (3); @a.perl.say;

On Sun Oct 09 09:13:19 2011, coke wrote: > On Wed Aug 11 13:25:39 2010, ronaldxs wrote: > > The variant my @a ||= (3); @a.perl.say; outputs something > reasonable. > > > > Ron > > Still happening: > > 12:11 < [Coke]> rakudo: my @a //= (3); @a.perl.say; > 12:11 <+p6eval> rakudo f6eb61: OUTPUT«m

[perl #68138] Rakudo tries to call role-parameter typename as a sub when using 'does' with a parameterized RHS && missing line# in the error

On Sun Aug 02 14:02:30 2009, eternal...@gmail.com wrote: > This code fails. Moritz believes it to be due to T not being bound when > Positional[T] appears. Also, the error has no line number. > > role TreeNode[::T] does Positional[T] { > has TreeNode[T] @!children handles 'postcircumfix:<[

[perl #80982] [BUG] No warning for non-octal numbers starting with 0 in Rakudo

Merged tickets. -- Will "Coke" Coleda

[perl6/specs] d067a9: Add a note about declarative semantics to the sect...

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: d067a9cb0d05aefbcda2c0328e7739aac746b830 https://github.com/perl6/specs/commit/d067a9cb0d05aefbcda2c0328e7739aac746b830 Author: pmichaud Date: 2012-06-29 (Fri, 29 Jun 2012) Changed paths: M S05-regex

showing more than one compilation error?

Is it possible to get more than one compilation error at once? Currently after the first undeclared variable Rakudo stops and I have many Once I fixed them it starts to complain the missing subs... A bit too much of running and editing and with the current start-up speed this is a bit discou

[perl6/specs] 9a7323: [S32::Exception] add Exception.fail

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9a732390c98161ab946457dfc6274353c2a4918b https://github.com/perl6/specs/commit/9a732390c98161ab946457dfc6274353c2a4918b Author: Moritz Lenz Date: 2012-06-29 (Fri, 29 Jun 2012) Changed paths: M S32-se

[perl #113904] [BUG] Null PMC Access when blocks get the wrong $_ sometimes in Rakudo

# New Ticket Created by "Carl Mäsak" # Please include the string: [perl #113904] # in the subject line of all future correspondence about this issue. # https://rt.perl.org:443/rt3/Ticket/Display.html?id=113904 > r: for Range.new(0, 1) -> $p { when $p { say $_.perl; say $_.path } } rakudo 39

[perl6/specs] 13a69e: [S32] Mu cleanup

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 13a69e809d4318045b8b8ee9eaa4d22b254f5095 https://github.com/perl6/specs/commit/13a69e809d4318045b8b8ee9eaa4d22b254f5095 Author: Moritz Lenz Date: 2012-06-29 (Fri, 29 Jun 2012) Changed paths: M S32-se

Re: say vs print for .WHAT

Moritz Lenz writes: > I've tried to answer that here: http://faq.perl6.org/#say Thanks. (And more than tried, I reckon you've succeeded.) Smylers -- http://twitter.com/Smylers2

Re: say vs print for .WHAT

Am 28.06.2012 23:43, schrieb Smylers: Patrick R. Michaud writes: print will stringify its arguments and write them to $*OUT. say will invoke .gist on its arguments and write them (along with a final newline) to $*OUT. Hi there. What's the rationale for the difference there? Under what circu