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 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:<6.2.7.1>; if you want to lock in a particular set of semantics at some greater degree of specificity." -y
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* perl6 to bend the rules; the problem is that nobody realized that p6doc was broken (this was discovered earlier today), so R* silently (grumble) didn't include it and you got some other p6doc instead. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
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 reasonable for stuff that is supposed to ship *with* perl6 to bend the rules; the problem is that nobody realized that p6doc was broken (this was discovered earlier today), so R* silently (grumble) didn't include it and you got some other p6doc instead. I agree with yary. I also think that dog-fooding it should be done where possible. If stuff that ships with perl6 can't be written using all the same best practices as code users should write, then its a problem. This includes not having "use v6.c". While exceptions may exist, any time they do, that should become a case study for whether there is truly a good reason for the code to work that way, or if there isn't. Keep in mind that the standard libraries are right now some of the primary examples Perl 6 developers would have to look at on how to write Perl 6 code. -- Darren Duncan
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 did have "use 6" at the top, then it would give a single more meaningful error... yet another reason for module authors to put "use 6" in their code. b) subject line should be "use 6.c", the "v" is depreciated... edited
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 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:<6.2.7.1>; > > if you want to lock in a particular set of semantics at some greater > degree of specificity." > > -y -- 4096R/EA75174B Steve Mynott
[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 2016) Changed paths: M S99-glossary.pod Log Message: --- point out ".ast" is an alternative to ".made".
