[perl #75592] Long running unclosed quotes trigger unhelpful message

On Sat Nov 17 11:40:48 2012, coke wrote: > On Mon Jun 07 14:23:47 2010, cognominal wrote: > > I am probably a lousy programmer but I hit again and again that > > unhelpful message. > > > > How to reproduce : > > > > eval "{\n\n\n\n\'}" > > > > Unable to parse blockoid, couldn't find final '}' at

[perl6/specs] acc460: S07: Fix small introspection details

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: acc4605bad27d1a136d47e5cc6790bdb2883d8e7 https://github.com/perl6/specs/commit/acc4605bad27d1a136d47e5cc6790bdb2883d8e7 Author: Moritz Lenz Date: 2015-09-12 (Sat, 12 Sep 2015)

[perl6/specs] 354bef: Clarify calling .cache more than once

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 354bef8e9856f41c842d4d5e20c2695b8e20b6c0 https://github.com/perl6/specs/commit/354bef8e9856f41c842d4d5e20c2695b8e20b6c0 Author: Tim Smith Date: 2015-09-12 (Sat, 12 Sep 2015)

[perl6/specs] 9855bf: typo

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 9855bfdc46dca7aec9d57f61ac58c0cafb87efa0 https://github.com/perl6/specs/commit/9855bfdc46dca7aec9d57f61ac58c0cafb87efa0 Author: raiph Date: 2015-09-12 (Sat, 12 Sep 2015) Changed

[perl6/specs] d1a719: Minor nit

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: d1a719192acc4089ecba68f9a33f65e01a62d20b https://github.com/perl6/specs/commit/d1a719192acc4089ecba68f9a33f65e01a62d20b Author: Elizabeth Mattijsen Date: 2015-09-12 (Sat, 12 Sep 2015)

[perl6/specs] 70844c: Fix typo

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 70844c1debf83690f4b30b1cfccf2b1267ea89e5 https://github.com/perl6/specs/commit/70844c1debf83690f4b30b1cfccf2b1267ea89e5 Author: Elizabeth Mattijsen Date: 2015-09-12 (Sat, 12 Sep 2015)

[perl6/specs] de53e4: Initial work on an S07 re-write.

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: de53e4be1241a36451e7f90c3902bedcdaab6a73 https://github.com/perl6/specs/commit/de53e4be1241a36451e7f90c3902bedcdaab6a73 Author: jnthn Date: 2015-09-12 (Sat, 12 Sep 2015) Changed paths:

[perl6/specs] fb7cb2: simplify / improve non-technical language

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: fb7cb20e2bdecc0f268e60f3d255f4c01c64dc12 https://github.com/perl6/specs/commit/fb7cb20e2bdecc0f268e60f3d255f4c01c64dc12 Author: raiph Date: 2015-09-12 (Sat, 12 Sep 2015) Changed

[perl6/specs] 6cc6cd: remove surplus 'an'

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 6cc6cd1fc43289bc9b9dad625bae160d64d77686 https://github.com/perl6/specs/commit/6cc6cd1fc43289bc9b9dad625bae160d64d77686 Author: Steve Mynott Date: 2015-09-14 (Mon, 14 Sep 2015)

[perl6/specs] 829e71: We *can* call .cache multiple times

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 829e71d8f27f9314328c28d3c9f94afacaccf994 https://github.com/perl6/specs/commit/829e71d8f27f9314328c28d3c9f94afacaccf994 Author: Elizabeth Mattijsen Date: 2015-09-12 (Sat, 12 Sep 2015)

[perl #126049] [BUG] Implicitly returning nothing from a subroutine returns an empty container

# New Ticket Created by Steve Schulze # Please include the string: [perl #126049] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=126049 > Post GLR, implicitly returning nothing from a subroutine now returns an empty

[perl #71544] [BUG] C arity sensitivity is too different from C

On Tue Jul 21 09:05:31 2015, lue wrote: > $ perl6 -e 'say (grep { $^a == $^b }, 1, 1, 2, 3, 4, 4).perl' > (1, 1, 4, 4) > > Works now, and there's a test in S32-list/grep.t So, closing ticket. Thanks! -- Will "Coke" Coleda

Market opportunity?

Neo4j, http://neo4j.com/ a graph database that looks interesting uses the JVM http://www.neo4j.org/java/jvm for its internal query language, Cipher http://neo4j.com/docs/stable/cypher-query-lang.html There could well be opportunities for Perl 6 to become an important part of the Neo4j ecosystem.

Proposed docs for C

Maybe a bit long, but think it explains it in a way people will understand. Thoughts? https://gist.github.com/dha/8009c28d7bf2d1ca8875 dha -- David H. Adler - - http://www.panix.com/~dha/ I think the scale of relative badness is broken in this place. - Diablo

Re: Proposed docs for C

Keep it on separate lines, I don't know how that formatting got lost (it's showing up as separate lines in my history). As for the rest of it, curious as to consensus. -y On Mon, Sep 14, 2015 at 4:06 PM, David H. Adler wrote: > On Mon, Sep 14, 2015 at 03:13:21PM -0400, yary

[perl6/specs] 3373e7: fix typo

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 3373e7261ace0f719c155bfc0f86668130ebe42a https://github.com/perl6/specs/commit/3373e7261ace0f719c155bfc0f86668130ebe42a Author: Lucien Grondin Date: 2015-09-14 (Mon, 14 Sep 2015)

[perl #123741] Rat.perl does not round-trip

I don't grasp everything of the quoted discussion, but the original evaluation works now as expected: $ perl6 -e 'say (2/6).WHAT; say (2/6).perl.EVAL.WHAT' (Rat) (Rat) A test was added to S32-scalar/perl.t with commit df84392d05. Is this ticket closeable?

[perl #123660] Confusion when using $_ as default

$ perl6-m -e 'sub a($a = CALLER::CALLER::<$_>) { say $a }; $_ = "foo"; a' foo $ perl6-m -e 'sub foo($a = CALLER::CALLER::<$_>) { say $a }; given 42 { foo(1); foo() }' 1 42 The ticket number is mentioned in S06-signature/caller-param.t. The following comment was added with commit 66a1ea8cb1: #

Re: [perl #125978] [BUG] Segfault (and other crashes) when using .hyper

http://irclog.perlgeek.de/perl6/2015-09-14#i_11216866 > 19:18 jnthn https://rt.perl.org/Ticket/Display.html?id=125978 seems stable > locally > 19:18 Perhaps thanks to my invocation race fixes > [...] > 19:19 jnthn cdc: Maybe you could test ^^ on latest I did some tests, and sadly it

Re: Proposed docs for C

On Mon, Sep 14, 2015 at 03:13:21PM -0400, yary wrote: > Using different numbers for the examples helps visualize what's > initialized vs added later: ... > *[1 2 3]next[1 2 3 3]next[1 2 3 3 3]* I don't know. I think, by having it on separate lines, and watching the row of '1's extend, is less

Re: Proposed docs for C

Using different numbers for the examples helps visualize what's initialized vs added later: sub a { *state @x = 1, 2;@x.push(3)*} =end code will continue to append each time it is called. So, =begin code say a; say "next"; say a; say "next"; say a; =end code will output =begin