Re: It's time to use "use v6.c"

On 2016-02-06 11:35 AM, Brandon Allbery wrote: On Sat, Feb 6, 2016 at 2:30 PM, yary wrote: this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 study group, and a helpful neighbor asked me to start up p6doc. This is something of an edge case. It is

[perl #127479] Attempting to dd a CallFrame object can throw an error in some cases

# New Ticket Created by Dave Rolsky # Please include the string: [perl #127479] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127479 > $ perl6 --version This is Rakudo version 2015.12-259-g5605d5f built on MoarVM version

It's time to use "use v6.c"

this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 study group, and a helpful neighbor asked me to start up p6doc. It gave me an error about EVAL being dangerous, and after opening a ticket & adding "use MONKEY-SEE-NO-EVAL" to my source, I got "Undeclared name:CompUnitRepo used

Re: It's time to use "use v6.c"

On Sat, Feb 6, 2016 at 2:30 PM, yary wrote: > this morning I installed the 2016.01 R*. Now I'm at the NYC perl6 > study group, and a helpful neighbor asked me to start up p6doc. > This is something of an edge case. It is reasonable for stuff that is supposed to ship *with*

Re: It's time to use "use v6.c"

Are you using windows? >From the recently updated http://perl6.org/downloads/ "p6doc was broken on Windows. Fix is to, with Git in the %PATH%, "panda --force install p6doc" and delete C:\rakudo\bin\p6doc.bat." S On 6 February 2016 at 19:30, yary wrote: > this morning I

[perl #127482] Compilation check says Syntax OK but program gets error

# New Ticket Created by James E Keenan # Please include the string: [perl #127482] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=127482 > The following program passes a compilation check but fails to run. # $ cat

Re: [perl #127482] Compilation check says Syntax OK but program gets error

On Sat, Feb 6, 2016 at 8:24 PM, James E Keenan wrote: > $ perl6 attempted_printf.pl6 > Type check failed in binding $format; expected Cool but got Pair > in block at attempted_printf.pl6 line 5 > The syntax is fine. The semantics aren't, and even simpler cases

[perl6/specs] b10af0: point out ".ast" is an alternative to ".made".

Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: b10af0c107266bd625e2de7ee61d1e75e87a3c88 https://github.com/perl6/specs/commit/b10af0c107266bd625e2de7ee61d1e75e87a3c88 Author: Timo Paulssen Date: 2016-02-06 (Sat, 06 Feb

Re: [perl #127482] Compilation check says Syntax OK but program gets error

On Sat, Feb 6, 2016 at 8:24 PM, James E Keenan wrote: > $ perl6 attempted_printf.pl6 > Type check failed in binding $format; expected Cool but got Pair > in block at attempted_printf.pl6 line 5 > The syntax is fine. The semantics aren't, and even simpler cases

Re: It's time to use "use 6.c"

Thanks all... I expect hiccups... just venting to help (future coders and current self)... while we're on this topic a) lwp-download.pl doesn't have a "use 6". Since Windows ignores the shebang, it invokes perl5 which is registered to handle "pl" files, and gives a bunch of syntax errors. If it