The windows p6doc fix at http://perl6.org/downloads/ has been updated.
On 6 February 2016 at 21:17, Steve Mynott <steve.myn...@gmail.com> wrote:
> 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."
> On 6 February 2016 at 19:30, yary <not....@gmail.com> 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. 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 at line 32"
>> And it looks like my p6doc is from an earlier install, circa July
>> 2015. Now, if back in July, p6doc had "use 6.0.0" in it, and if today,
>> Rakudo would see that and say "ah back then we didn't need
>> SEE-NO-EVAL," then p6doc would still work.
>> Please module authors, start using "use 6.c;" at the top of your
>> modules. Please Rakudo contributors, consider making spec
>> compatibility as described in S11 a reality:
>> "say something like
>> use Perl:<6.0>;
>> use Perl:<6.0.0>;
>> use Perl:<18.104.22.168>;
>> if you want to lock in a particular set of semantics at some greater
>> degree of specificity."
> 4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>
4096R/EA75174B Steve Mynott <steve.myn...@gmail.com>