perl.perl6.language http://www.nntp.perl.org/group/perl.perl6.language/ ... Copyright 1998-2016 perl.org Sat, 27 Aug 2016 01:09:39 +0000 ask@perl.org [perl6/specs] 151d79: Revert "Forbid Bare C<\b> in Regexes" by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 151d791563ce474709ed38984f883a05ad73dc0b<br/> https://github.com/perl6/specs/commit/151d791563ce474709ed38984f883a05ad73dc0b<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-08-25 (Thu, 25 Aug 2016)<br/><br/> Changed paths:<br/> M v6d.pod<br/><br/> Log Message:<br/> -----------<br/> Revert &quot;Forbid Bare C&lt;\b&gt; in Regexes&quot;<br/><br/>This reverts commit b14828bb01abb7e659b9f1a4d43ba572d3a4f173.<br/>Per discussion with pmichaud++, this can be added right now, without<br/>waiting for 6.d:<br/>https://github.com/perl6/specs/commit/b14828bb01abb7e659b9f1a4d43ba572d3a4f173#commitcomment-18777938<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/08/msg36642.html Fri, 26 Aug 2016 09:28:15 +0000 [perl6/specs] b14828: Forbid Bare C<\b> in Regexes by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: b14828bb01abb7e659b9f1a4d43ba572d3a4f173<br/> https://github.com/perl6/specs/commit/b14828bb01abb7e659b9f1a4d43ba572d3a4f173<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-08-24 (Wed, 24 Aug 2016)<br/><br/> Changed paths:<br/> M v6d.pod<br/><br/> Log Message:<br/> -----------<br/> Forbid Bare C&lt;\b&gt; in Regexes<br/><br/>Implementation to close RT#128986<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/08/msg36641.html Thu, 25 Aug 2016 14:35:38 +0000 [perl6/specs] 2e72b5: Display historical message based on <body> andnot... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 2e72b5d1d8f06674b14fef0ba818079eb9189436<br/> https://github.com/perl6/specs/commit/2e72b5d1d8f06674b14fef0ba818079eb9189436<br/> Author: Zoffix Znet &lt;zoffixznet@users.noreply.github.com&gt;<br/> Date: 2016-08-09 (Tue, 09 Aug 2016)<br/><br/> Changed paths:<br/> M html/perl-with-historical-message.css<br/><br/> Log Message:<br/> -----------<br/> Display historical message based on &lt;body&gt; and not &lt;html&gt;<br/><br/>Fixes rendering issues on rekonq<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/08/msg36640.html Tue, 09 Aug 2016 23:01:30 +0000 [perl6/specs] 899560: Add v6d.pod, a place to track proposedlanguage ch... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 899560e86ad0279925dd8beb80f108d319aa40fc<br/> https://github.com/perl6/specs/commit/899560e86ad0279925dd8beb80f108d319aa40fc<br/> Author: Moritz Lenz &lt;moritz@faui2k3.org&gt;<br/> Date: 2016-08-09 (Tue, 09 Aug 2016)<br/><br/> Changed paths:<br/> A v6d.pod<br/><br/> Log Message:<br/> -----------<br/> Add v6d.pod, a place to track proposed language changes for v6.d<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/08/msg36639.html Tue, 09 Aug 2016 23:01:30 +0000 [perl6/specs] ce2925: Add: Signature/Attribute Defaults Based onDefined... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: ce29255b71b1a29334ab0028a678f83c3fc51ceb<br/> https://github.com/perl6/specs/commit/ce29255b71b1a29334ab0028a678f83c3fc51ceb<br/> Author: Zoffix Znet &lt;zoffixznet@users.noreply.github.com&gt;<br/> Date: 2016-08-09 (Tue, 09 Aug 2016)<br/><br/> Changed paths:<br/> M v6d.pod<br/><br/> Log Message:<br/> -----------<br/> Add: Signature/Attribute Defaults Based on Definedness<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/08/msg36638.html Tue, 09 Aug 2016 23:01:29 +0000 Announce: Rakudo Star Release 2016.07 by Steve Mynott On behalf of the Rakudo and Perl 6 development teams, I&rsquo;m pleased to <br/>announce the July 2016 release of &ldquo;Rakudo Star&rdquo;, a useful and usable <br/>production distribution of Perl 6. The tarball for the July 2016 release is <br/>available from http://rakudo.org/downloads/star/. <br/> <br/>This is the third post-Christmas (production) release of Rakudo Star and <br/>implements Perl v6.c. It comes with support for the MoarVM backend (all <br/>module tests pass on supported platforms). <br/> <br/>Please note that this release of Rakudo Star is not fully functional with <br/>the JVM backend from the Rakudo compiler. Please use the MoarVM backend <br/>only. <br/> <br/>In the Perl 6 world, we make a distinction between the language (&ldquo;Perl 6&Prime;) <br/>and specific implementations of the language such as &ldquo;Rakudo Perl&rdquo;. This <br/>Star release includes release 2016.07 of the Rakudo Perl 6 compiler, <br/>version 2016.07 of MoarVM, plus various modules, documentation, and other <br/>resources collected from the Perl 6 community. <br/> <br/>Some of the new compiler features since the last Rakudo Star release <br/>include: <br/> <br/>+ Ability to use a customer debugger module <br/>+ The &ldquo;is-approx&rdquo; sub from Test.pm6 now allows for relative/absolute <br/>tolerance <br/>+ A fail in a custom BUILD will now be returned, rather than thrown <br/>+ Introduce .Map coercer <br/>+ Implement alternate ways to call subtest <br/>+ Support for new leap-second at the end of 2016 <br/>+ The &ldquo;is required&rdquo; trait on Attributes can now take a Bool or a Str <br/>+ IO::[Path,Handle] gained a .mode method which returns the POSIX file <br/>permissions <br/>+ Distribution is now a role interface that enables encapsulating IO used <br/>for distribution installation <br/>+ CompUnit::Repository::Installation now uses the new Distribution interface <br/>+ Custom repository implementations now supported, including precompilation <br/> <br/>Compiler maintenance since the last Rakudo Star release includes: <br/> <br/>+ Basic object creation (using either .new or .bless) now up to 3x faster <br/>+ All routines now have less overhead <br/>+ The MMD cache accepts candidates with named parameters if it can. (This <br/>made adverbed slices about 18x as fast) <br/>+ Sigificant optimizations for speed in many parts of the system (.map, <br/>gather/take etc.) <br/>+ Many precompilation fixes (including EVAL and improved support of OS <br/>packaging) <br/>+ Arrays with holes (e.g. from :delete) now correctly iterate/auto-vivify <br/>+ An issue with reverse dependencies of installed modules was fixed <br/>+ &ldquo;is_approx&rdquo; sub (note underscore) from Test.pm6 deprecated <br/>+ Harden Mu.Str against moving GC <br/>+ Simplify $USER/$GROUP initialization <br/>+ Mu can now be the result of a Promise <br/>+ samewith() now also works on non-multi&rsquo;s <br/>+ Many fixes in the area of pre-compilation and installing modules <br/>+ count-only and bool-only now are optional methods in Iterators (only to <br/>be implemented if they can work without generating anything) <br/>+ IO::ArgFiles.slurp / IO::ArgFiles.eof are fixed <br/>+ REPL whitespace and error handling <br/>+ CompUnit::Repository::Installation no longer considers bin/xxx and <br/>resources/bin/xxx the same content address <br/>+ min/max on Failures throw instead of returning &plusmn;Inf <br/>+ NativeCall&rsquo;s is mangled trait no longer ignored for CPPStruct <br/>+ Many Str, List and Array methods much faster <br/>+ Map/Hash initializations are now 30% faster <br/>+ make DESTDIR now correctly finds CompUnit::Repository::Staging <br/>+ Output from Test.pm6&prime;s diag() is no longer lost in non-verbose prove <br/>output when called at the start of the test file or during TODO tests <br/>+ Improved error messages <br/> <br/>Notable changes in modules shipped with Rakudo Star: <br/> <br/>+ DBIish: v0.5.9 (with many Oracle/MySQL fixes) plus README.pod and <br/>mojibake fixes <br/>+ NativeHelpers-Blob: v0.1.10 <br/>+ PSGI: v1.2.0 supports P6SGI 0.7Draft <br/>+ Pod-To-HTML: v0.1.2 plus fixes <br/>+ debugger-ui-commandline: README fixes <br/>+ doc: many fixes to documentation content and HTML generation <br/>+ panda: Avoid Rakudo internals deprecation warning and don&rsquo;t require <br/>Build.pm to inherit Panda::Builder <br/>+ perl6-file-which: CI fixes <br/>+ perl6-http-easy: v1.1.0 (with more flexible P6SGI support) plus avoid <br/>errors in binary request <br/>+ shell-command: Mention already implemented commands missing from README <br/>+ perl6-lwp-simple: track github.com/perl6/perl6-lwp-simple as upstream (as <br/>panda does) which has a test fix needed since we don&rsquo;t support https in R* <br/>and a test url had a new https redirect <br/> <br/>perl6intro.pdf has also been updated. <br/> <br/>There are some key features of Perl 6 that Rakudo Star does not yet handle <br/>appropriately, although they will appear in upcoming releases. Some of the <br/>not-quite-there features include: <br/> <br/>+ advanced macros <br/>+ non-blocking I/O (in progress) <br/>+ some bits of Synopsis 9 and 11 <br/>+ There is an online resource at http://perl6.org/compilers/features that <br/>lists the known implemented and missing features of Rakudo&rsquo;s backends and <br/>other Perl 6 implementations. <br/> <br/>In many places we&rsquo;ve tried to make Rakudo smart enough to inform the <br/>programmer that a given feature isn&rsquo;t implemented, but there are many that <br/>we&rsquo;ve missed. Bug reports about missing and broken features are welcomed at <br/>rakudobug@perl.org. <br/> <br/>See http://perl6.org/ for links to much more information about Perl 6, <br/>including documentation, example code, tutorials, presentations, reference <br/>materials, design documents, and other supporting resources. Some Perl 6 <br/>tutorials are available under the &ldquo;docs&rdquo; directory in the release tarball. <br/> <br/>The development team thanks all of the contributors and sponsors for making <br/>Rakudo Star possible. If you would like to contribute, see <br/>http://rakudo.org/how-to-help, ask on the perl6-compiler@perl.org mailing <br/>list, or join us on IRC #perl6 on freenode. <br/> <br/> <br/>-- <br/>4096R/EA75174B Steve Mynott &lt;steve.mynott@gmail.com&gt; http://www.nntp.perl.org/group/perl.perl6.language/2016/07/msg36637.html Fri, 22 Jul 2016 11:00:23 +0000 [perl6/specs] be783f: prohibit mixing visible and non-visible columnsep... by GitHub Branch: refs/heads/master <br/> Home: https://github.com/perl6/specs <br/> Commit: be783f75c4a0e58ce5588e304f8163cb32fca8e8 <br/> https://github.com/perl6/specs/commit/be783f75c4a0e58ce5588e304f8163cb32fca8e8 <br/> Author: Tom Browder &lt;tom.browder@gmail.com&gt; <br/> Date: 2016-07-11 (Mon, 11 Jul 2016) <br/> <br/> Changed paths: <br/> M S26-documentation.pod <br/> <br/> Log Message: <br/> ----------- <br/> prohibit mixing visible and non-visible column separator types in a table <br/> <br/> <br/> Commit: 837c3d8c779575a31df5dc213ef543f0fd372096 <br/> https://github.com/perl6/specs/commit/837c3d8c779575a31df5dc213ef543f0fd372096 <br/> Author: Tom Browder &lt;tom.browder@gmail.com&gt; <br/> Date: 2016-07-11 (Mon, 11 Jul 2016) <br/> <br/> Changed paths: <br/> M S26-documentation.pod <br/> <br/> Log Message: <br/> ----------- <br/> Merge pull request #114 from tbrowder/col-sep-restriction <br/> <br/>prohibit mixing visible and non-visible column separator types in a t&hellip; <br/> <br/> <br/>Compare: https://github.com/perl6/specs/compare/15c158609c3c...837c3d8c7795= http://www.nntp.perl.org/group/perl.perl6.language/2016/07/msg36636.html Tue, 12 Jul 2016 19:28:18 +0000 [perl6/specs] f8a00d: further amplify table row and cell requirmentsand... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: f8a00d19534d03ffb3cfb49fc4eee58d79ec1417<br/> https://github.com/perl6/specs/commit/f8a00d19534d03ffb3cfb49fc4eee58d79ec1417<br/> Author: Tom Browder &lt;tom.browder@gmail.com&gt;<br/> Date: 2016-07-04 (Mon, 04 Jul 2016)<br/><br/> Changed paths:<br/> M S26-documentation.pod<br/><br/> Log Message:<br/> -----------<br/> further amplify table row and cell requirments and recommendations<br/><br/><br/> Commit: 135839ce478ba2b013c0cb21b9038996dc7f80ea<br/> https://github.com/perl6/specs/commit/135839ce478ba2b013c0cb21b9038996dc7f80ea<br/> Author: Tom Browder &lt;tom.browder@gmail.com&gt;<br/> Date: 2016-07-06 (Wed, 06 Jul 2016)<br/><br/> Changed paths:<br/> M S26-documentation.pod<br/><br/> Log Message:<br/> -----------<br/> add expectation of the same number of cells per row<br/><br/><br/> Commit: 15c158609c3c6c1e9640aa11dccb21ea8fbf4cc8<br/> https://github.com/perl6/specs/commit/15c158609c3c6c1e9640aa11dccb21ea8fbf4cc8<br/> Author: Tom Browder &lt;tom.browder@gmail.com&gt;<br/> Date: 2016-07-06 (Wed, 06 Jul 2016)<br/><br/> Changed paths:<br/> M S26-documentation.pod<br/><br/> Log Message:<br/> -----------<br/> Merge pull request #112 from tbrowder/pod-table-fix<br/><br/>further amplify table row and cell requirments and recommendations<br/><br/><br/>Compare: https://github.com/perl6/specs/compare/00805498c2c6...15c158609c3c http://www.nntp.perl.org/group/perl.perl6.language/2016/07/msg36635.html Thu, 07 Jul 2016 13:05:08 +0000 [perl6/specs] fc36bc: clarify use of column separators by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: fc36bc28f97b792e5668b73e5be8c5ede870f9c3<br/> https://github.com/perl6/specs/commit/fc36bc28f97b792e5668b73e5be8c5ede870f9c3<br/> Author: Tom Browder &lt;tom.browder@gmail.com&gt;<br/> Date: 2016-07-04 (Mon, 04 Jul 2016)<br/><br/> Changed paths:<br/> M S26-documentation.pod<br/><br/> Log Message:<br/> -----------<br/> clarify use of column separators<br/><br/><br/> Commit: 00805498c2c6aed3e599d91b759668da965d93f6<br/> https://github.com/perl6/specs/commit/00805498c2c6aed3e599d91b759668da965d93f6<br/> Author: lizmat &lt;liz@dijkmat.nl&gt;<br/> Date: 2016-07-05 (Tue, 05 Jul 2016)<br/><br/> Changed paths:<br/> M S26-documentation.pod<br/><br/> Log Message:<br/> -----------<br/> Merge pull request #111 from tbrowder/doc-table-mod<br/><br/>clarify use of column separators<br/><br/><br/>Compare: https://github.com/perl6/specs/compare/6c5859544608...00805498c2c6 http://www.nntp.perl.org/group/perl.perl6.language/2016/07/msg36634.html Mon, 04 Jul 2016 23:53:44 +0000 [perl6/specs] 6c5859: Change nbsp to space in "Perl Hacker". by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 6c585954460888c3526b5dacf269847117d30850<br/> https://github.com/perl6/specs/commit/6c585954460888c3526b5dacf269847117d30850<br/> Author: Bruce Gray &lt;bruce.gray@acm.org&gt;<br/> Date: 2016-06-27 (Mon, 27 Jun 2016)<br/><br/> Changed paths:<br/> M S03-operators.pod<br/><br/> Log Message:<br/> -----------<br/> Change nbsp to space in &quot;Perl Hacker&quot;.<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36633.html Tue, 28 Jun 2016 16:12:46 +0000 Re: Intalling Perl6 by Brandon Allbery On Sun, Jun 26, 2016 at 1:51 PM, Julian Brown &lt;jlbprof@gmail.com&gt; wrote:<br/><br/>&gt; I search for packages on Debian Jessie for Perl 6 and found Rakudo and<br/>&gt; Parrot.<br/>&gt;<br/>&gt; Does everyone install per user and not system-wide?<br/>&gt; Does anyone use Parrot instead of Moar?<br/>&gt;<br/><br/>Debian is, as always, way behind. The Parrot backend hasn&#39;t even been<br/>supported for over a year. (There should be be newer packages in unstable,<br/>and possibly already in testing.)<br/><br/>System-wide installation was broken when the new CompUnitRepo stuff was<br/>added, and was only recently fixed --- but still needs more testing, so if<br/>you choose to do a system-wide install of a sufficiently recent rakudo (I<br/>think this means 2016.05 or later) you should expect to be a guinea pig.<br/><br/>-- <br/>brandon s allbery kf8nh sine nomine associates<br/>allbery.b@gmail.com ballbery@sinenomine.net<br/>unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36632.html Sun, 26 Jun 2016 18:00:48 +0000 Intalling Perl6 by Julian Brown I am on Debian Jessie.<br/><br/>I went to the Rakudo.org and looked at &quot;how to get it&quot; page and it only<br/>offers ways to install it for a particular user, there does not seem to be<br/>instructions on how to make it system wide.<br/><br/>I was under the impression I wanted Rakudo and Moar.<br/><br/>I search for packages on Debian Jessie for Perl 6 and found Rakudo and<br/>Parrot.<br/><br/>Does everyone install per user and not system-wide?<br/>Does anyone use Parrot instead of Moar?<br/><br/>Thanx<br/><br/>Julian http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36631.html Sun, 26 Jun 2016 17:51:43 +0000 doc.perl6.org cert expired on 6/25/2016 by Julian Brown http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36630.html Sun, 26 Jun 2016 13:48:11 +0000 [perl6/specs] 340c68: Change @*INC to @?INC , which was missed incommit... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 340c686f87e1597627507d8fd6fddd699f82c2e7<br/> https://github.com/perl6/specs/commit/340c686f87e1597627507d8fd6fddd699f82c2e7<br/> Author: Bruce Gray &lt;bruce.gray@acm.org&gt;<br/> Date: 2016-06-22 (Wed, 22 Jun 2016)<br/><br/> Changed paths:<br/> M S28-special-names.pod<br/><br/> Log Message:<br/> -----------<br/> Change @*INC to @?INC , which was missed in commit dd31858<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36629.html Thu, 23 Jun 2016 05:46:20 +0000 [perl6/specs] f9061b: Clarify note by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: f9061b3ee7a777e77e89f04fba47a0ec5a8954e0<br/> https://github.com/perl6/specs/commit/f9061b3ee7a777e77e89f04fba47a0ec5a8954e0<br/> Author: Zoffix Znet &lt;zoffixznet@users.noreply.github.com&gt;<br/> Date: 2016-06-10 (Fri, 10 Jun 2016)<br/><br/> Changed paths:<br/> M html/perl.css<br/><br/> Log Message:<br/> -----------<br/> Clarify note<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36628.html Sat, 11 Jun 2016 22:15:00 +0000 [perl6/specs] 55ef20: Add a note about used on multiple sites. by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 55ef20a63b1e6920292acf85e9c44a88682f9ec3<br/> https://github.com/perl6/specs/commit/55ef20a63b1e6920292acf85e9c44a88682f9ec3<br/> Author: Zoffix Znet &lt;zoffixznet@users.noreply.github.com&gt;<br/> Date: 2016-06-10 (Fri, 10 Jun 2016)<br/><br/> Changed paths:<br/> M html/perl.css<br/><br/> Log Message:<br/> -----------<br/> Add a note about used on multiple sites.<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/06/msg36627.html Sat, 11 Jun 2016 22:14:54 +0000 [perl6/specs] 3a3148: Offset :target by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 3a3148d2391a1be03f097eb649ce7908a7f47582<br/> https://github.com/perl6/specs/commit/3a3148d2391a1be03f097eb649ce7908a7f47582<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-05-31 (Tue, 31 May 2016)<br/><br/> Changed paths:<br/> M html/perl-with-historical-message.css<br/> M html/style.css<br/><br/> Log Message:<br/> -----------<br/> Offset :target<br/><br/>To ensure it&quot;s first lines aren&quot;t covered by historical message when visiting a direct link to section<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36626.html Tue, 31 May 2016 17:25:48 +0000 [perl6/specs] 9a8149: Match historical message style with that ofauto-g... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 9a8149f939580523d3fb25d0611d0d03d17e9886<br/> https://github.com/perl6/specs/commit/9a8149f939580523d3fb25d0611d0d03d17e9886<br/> Author: Zoffix Znet &lt;zoffixznet@users.noreply.github.com&gt;<br/> Date: 2016-05-31 (Tue, 31 May 2016)<br/><br/> Changed paths:<br/> M html/style.css<br/><br/> Log Message:<br/> -----------<br/> Match historical message style with that of auto-generated subpages<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36625.html Tue, 31 May 2016 17:25:47 +0000 [perl6/specs] fd990b: Use less of an eye-bleed color and betterposition... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: fd990bf57d6429e21c37b01eae9036f8c1391fcb<br/> https://github.com/perl6/specs/commit/fd990bf57d6429e21c37b01eae9036f8c1391fcb<br/> Author: Zoffix Znet &lt;zoffixznet@users.noreply.github.com&gt;<br/> Date: 2016-05-30 (Mon, 30 May 2016)<br/><br/> Changed paths:<br/> M html/perl-with-historical-message.css<br/><br/> Log Message:<br/> -----------<br/> Use less of an eye-bleed color and better positioning for historical message<br/><br/>MadcapJake++<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36624.html Tue, 31 May 2016 17:25:29 +0000 [perl6/specs] d9fab8: Revert "Add outdatedness note to secondstylesheet... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: d9fab8171bb2c6aa45095e3572f94e620c26c367<br/> https://github.com/perl6/specs/commit/d9fab8171bb2c6aa45095e3572f94e620c26c367<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-05-23 (Mon, 23 May 2016)<br/><br/> Changed paths:<br/> M html/perl.css<br/><br/> Log Message:<br/> -----------<br/> Revert &quot;Add outdatedness note to second stylesheet used by the site as well&quot;<br/><br/>This reverts commit 337e775a8511ad6cef00924cb9a71a57cc6b7785.<br/><br/>The sheet is used on other sites too.<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36623.html Tue, 24 May 2016 13:21:53 +0000 [perl6/specs] 479182: Add note that specs may be outdated on eachpage (... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 479182221597c209a95c0ddb2456afb535fd646d<br/> https://github.com/perl6/specs/commit/479182221597c209a95c0ddb2456afb535fd646d<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-05-23 (Mon, 23 May 2016)<br/><br/> Changed paths:<br/> M html/style.css<br/><br/> Log Message:<br/> -----------<br/> Add note that specs may be outdated on each page (Closes #110)<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36622.html Tue, 24 May 2016 13:21:52 +0000 [perl6/specs] 04b3cc: Work around the issue of multiple sites usingperl... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 04b3cc68498256c0a52bbbd0d72f8b6ee451c696<br/> https://github.com/perl6/specs/commit/04b3cc68498256c0a52bbbd0d72f8b6ee451c696<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-05-23 (Mon, 23 May 2016)<br/><br/> Changed paths:<br/> A html/perl-with-historical-message.css<br/><br/> Log Message:<br/> -----------<br/> Work around the issue of multiple sites using perl.css<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36621.html Tue, 24 May 2016 13:21:51 +0000 [perl6/specs] 337e77: Add outdatedness note to second stylesheetused by... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 337e775a8511ad6cef00924cb9a71a57cc6b7785<br/> https://github.com/perl6/specs/commit/337e775a8511ad6cef00924cb9a71a57cc6b7785<br/> Author: Zoffix Znet &lt;cpan@zoffix.com&gt;<br/> Date: 2016-05-23 (Mon, 23 May 2016)<br/><br/> Changed paths:<br/> M html/perl.css<br/><br/> Log Message:<br/> -----------<br/> Add outdatedness note to second stylesheet used by the site as well<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36620.html Tue, 24 May 2016 13:21:46 +0000 Re: can a method name contain a funny character? by yary Thanks for the in-depth analysis. My misunderstanding was about what an<br/>identifier considers a number; I have no well-thought-out ideas on the<br/>subject of what an identifier ought to be.<br/><br/>Having the docs mention that &quot;number&quot; means only characters with a Unicode<br/>Property GeneralCategory of Nd might have prevented me from looking through<br/>the NumericTypes for a pattern. With more experimenting, I might have<br/>noticed that De was the one that always worked, since De has a one-to-one<br/>correspondence with Nd...<br/><br/>-y http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36619.html Sat, 21 May 2016 17:20:13 +0000 Re: can a method name contain a funny character? by Larry Wall On Fri, May 20, 2016 at 09:39:30AM -0400, yary wrote:<br/>: On Tue, Apr 12, 2016 at 6:12 PM, Brandon Allbery &lt;allbery.b@gmail.com&gt;<br/>: wrote:<br/>: &gt; I was explaining why some &quot;symbols&quot; are acceptable to the parser. Which<br/>: one<br/>: &gt; is more appropriate is not my call,<br/>: <br/>: I was thinking about what exactly are valid identifiers in Perl6/rakudo&#39;s<br/>: implementation. The docs &lt;http://docs.perl6.org/language/syntax#Identifiers&gt;<br/>: say:<br/>: <br/>: An identifier is a primitive name, and must start with an alphabetic<br/>: character (or an underscore), followed by zero or more word characters<br/>: (alphabetic, underscore or number). You can also embed dashes - or single<br/>: quotes &#39; in the middle, but not two in a row.<br/><br/>At this point, &quot;number&quot; means only characters with a GeneralCategory<br/>of Nd. We could talk about generalizing that, but there are potential<br/>issues. We can&#39;t simply extend it to No characters, because then<br/><br/> pi&sup2;<br/><br/>would misparse as a 3-character identifier.<br/><br/>: Experimenting with some of the numeric codes from Wikipedia<br/>: &lt;https://en.wikipedia.org/wiki/Numerals_in_Unicode&gt;, some of the numeric<br/>: codes seem inconsistent-<br/><br/>Note that, even if we used this table, we could not distinguish &sup2; from &#x2461; and such.<br/><br/>: &gt; my $_&#x96C;&#xCEC;&#x1D7E8; = &#x96C;&#xCEC;&#x1D7E8; # &quot;De&quot; Devanagari, Kannada, Mathematical. &quot;De&quot; is all<br/>: good.<br/>: 666<br/><br/>That&#39;s fine, those work because of the Nd general property, so they&#39;re equivalent<br/>to 0..9 as far as we&#39;re concerned.<br/><br/>: &gt; my $x&#x516D; = 6 # &quot;Nu&quot; Han number 6<br/>: 6<br/>: &gt; say &#x516D;<br/>: ===SORRY!=== ...<br/><br/>Note that &#x516D; works in identifiers by virtue of being not numeric at all,<br/>but by being in general category Lo, that is, it&#39;s a &quot;letter other&quot;,<br/>so considered alphabetic.<br/><br/>: &gt; say &#xBF0; # &quot;Nu&quot; Tamil number 10<br/>: 10<br/>: &gt; my $x&#xBF0; = 5<br/>: ===SORRY!=== Error ...<br/><br/>Excluded because it&#39;s No, not Nd.<br/><br/>: &gt; say &#x2460; + 3 # &quot;Di&quot; 1 in typographic context has value 1<br/>: 4<br/>: &gt; my $b&#x2460; = 44 &quot;Di&quot; 1 not valid in identifier<br/>: ===SORRY!=== Error ...<br/><br/>&#x2460; is indistinguishable from superscripts, even by &quot;Di&quot;, and falls into<br/>the No general category, so excluded.<br/><br/>: Some numeric codepoints are recognized as such, yet Rakudo isn&#39;t allowing<br/>: them in identifiers. Especially confounding is the treatment of the &quot;Han<br/>: number 6&quot; and &quot;Tamil number 10&quot;, both of which are unicode &quot;Nu&quot; numeric.<br/>: The Tamil is recognized as a number on its own but not as an identifier;<br/>: the Han is allowed in an identifier but isn&#39;t recognized as a number!<br/><br/>We currently rely only on GeneralCategory. I don&#39;t believe we use<br/>NumericType anywhere in parsing Perl 6.<br/><br/>: Is there some deeper rule at work here- which could be added to the<br/>: documentation? Or are these bugs?<br/><br/>Not a bug, but potentially negotiable. It simply comes down to Nd vs<br/>No at the moment. One could argue that we could notice superscripts<br/>as a separate category and treat them differently, but there are two<br/>arguments against that.<br/><br/>The first is that we&#39;d like to keep the basic identifier rules fairly<br/>simple. We&#39;re already pushing the state of the art here, and I don&#39;t<br/>see much benefit in making the rules more arcane that they are.<br/><br/>The second argument is that we should probably reserve syntax for the<br/>user here. Once we get slangs fully hooked up, we can easily let users<br/>define identifiers to include &#x2460; and such. But it&#39;s just as likely,<br/>perhaps more likely, that the user will want to use &#x2460; for a postfix,<br/>just like we currently treat superscripts as powers. We can&#39;t guess<br/>(well, we *could* guess, but can&#39;t know) which way the user will want to<br/>use these, so the conservative approach is to make neither of them work,<br/>and let the user take an additive approach, rather than forcing them to<br/>use a subtractive approach if we guessed wrong.<br/><br/>Larry<br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36618.html Sat, 21 May 2016 16:57:45 +0000 Re: can a method name contain a funny character? by yary To be clear, I expect that &quot;number&quot; in &quot;followed by zero or more word<br/>characters (alphabetic, underscore or number)&quot; means &quot;if Unicode thinks<br/>it&#39;s numeric, you can use it in an identifier after the first character.&quot;<br/><br/>I don&#39;t expect that every numeric codepoint in Unicode must evaluate to<br/>number in the Perl6 settings. We can have Numeric::Roman,<br/>Numeric::Counting-Rod, Numeric::Euler etc. for those, if someone cares<br/>enough to write &amp; use them. http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36617.html Fri, 20 May 2016 14:12:25 +0000 Re: can a method name contain a funny character? by yary On Tue, Apr 12, 2016 at 6:12 PM, Brandon Allbery &lt;allbery.b@gmail.com&gt; <br/>wrote: <br/>&gt; I was explaining why some &quot;symbols&quot; are acceptable to the parser. Which <br/>one <br/>&gt; is more appropriate is not my call, <br/> <br/>I was thinking about what exactly are valid identifiers in Perl6/rakudo&#39;s <br/>implementation. The docs &lt;http://docs.perl6.org/language/syntax#Identifiers&gt; <br/>say: <br/> <br/>An identifier is a primitive name, and must start with an alphabetic <br/>character (or an underscore), followed by zero or more word characters <br/>(alphabetic, underscore or number). You can also embed dashes - or single <br/>quotes &#39; in the middle, but not two in a row. <br/> <br/> <br/>Experimenting with some of the numeric codes from Wikipedia <br/>&lt;https://en.wikipedia.org/wiki/Numerals_in_Unicode&gt;, some of the numeric <br/>codes seem inconsistent- <br/> <br/>&gt; my $_&#x96C;&#xCEC;&#x1D7E8; = &#x96C;&#xCEC;&#x1D7E8; # &quot;De&quot; Devanagari, Kannada, Mathematical. &quot;De&quot; is all <br/>good. <br/>666 <br/> <br/>&gt; my $x&#x516D; = 6 # &quot;Nu&quot; Han number 6 <br/>6 <br/>&gt; say &#x516D; <br/>===SORRY!=== ... <br/>&gt; say &#xBF0; # &quot;Nu&quot; Tamil number 10 <br/>10 <br/>&gt; my $x&#xBF0; = 5 <br/>===SORRY!=== Error ... <br/> <br/>&gt; say &#x2460; + 3 # &quot;Di&quot; 1 in typographic context has value 1 <br/>4 <br/>&gt; my $b&#x2460; = 44 &quot;Di&quot; 1 not valid in identifier <br/>===SORRY!=== Error ... <br/> <br/>Some numeric codepoints are recognized as such, yet Rakudo isn&#39;t allowing <br/>them in identifiers. Especially confounding is the treatment of the &quot;Han <br/>number 6&quot; and &quot;Tamil number 10&quot;, both of which are unicode &quot;Nu&quot; numeric. <br/>The Tamil is recognized as a number on its own but not as an identifier; <br/>the Han is allowed in an identifier but isn&#39;t recognized as a number! <br/> <br/>Is there some deeper rule at work here- which could be added to the <br/>documentation? Or are these bugs? <br/> <br/>-y http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36616.html Fri, 20 May 2016 13:39:57 +0000 Re: Unwanted failure and FAILGOAL by Moritz Lenz Hi,<br/><br/>On 05/11/2016 07:45 AM, Richard Hainsworth wrote:<br/>&gt; I have the following in a grammar<br/>&gt;<br/>&gt; rule TOP { ^ &lt;statement&gt;+ $ };<br/>&gt;<br/>&gt; rule statement { &lt;id&gt; &#39;=&#39; &lt;endvalue&gt;<br/>&gt; | { { self.panic($/, &quot;Declaration syntax<br/>&gt; incorrect&quot;) } }<br/>&gt; };<br/>&gt;<br/>&gt; rule endvalue { &lt;keyword&gt; &#39;(&#39; ~ &#39;)&#39; &lt;pairlist&gt;<br/>&gt; | { self.panic($/, &quot;Invalid declaration.&quot;) }<br/>&gt; }<br/>&gt;<br/>&gt; The grammar parses a correct input file up until the end of the file. At<br/>&gt; that point even if there is no un-consumed input, there is an attempt to<br/>&gt; match &lt;id&gt;, which fails. The failure causes the panic with &#39;Declaration<br/>&gt; syntax&#39;.<br/>&gt;<br/>&gt; Am I missing something simple here?<br/>&gt;<br/>&gt; I would have thought (though this is only a very newbie assumption)<br/>&gt; that if the end of the input being sent to the grammar has been reached<br/>&gt; after the last &lt;statement&gt; has been matched, then there should be no<br/>&gt; reason for the parse method to try to match &lt;statement&gt; again, and if it<br/>&gt; fails to test for the end of input.<br/><br/>This is not how regexes or grammars work.<br/><br/>The + quantifier tries as many times as possible to match the regex. It <br/>doesn&#39;t look ahead to see if more characters are available, and it <br/>doesn&#39;t know about the end-of-string anchor that comes next in the grammar.<br/><br/>In fact, it doesn&#39;t know if the rule it quantifies might have a way to <br/>match zero characters. In this case, it would be wrong behavior to not <br/>do a zero-width at the end of the string.<br/><br/>As for improving the error reporting from within a grammar, there are <br/>lots of way to get creative, and I&#39;d urge you to read Perl 6&#39;s own <br/>grammar, which is a good inspiration for that.<br/>See https://github.com/rakudo/rakudo/blob/nom/src/Perl6/Grammar.nqp<br/><br/>One thing you could do is structure the statement rule differently:<br/><br/>rule statement {<br/> &lt;id&gt;<br/> [ &#39;=&#39; &lt;endvalue&gt;<br/> || { self.panic($/, &quot;Invalid declaration.&quot;)<br/> ]<br/>}<br/><br/>And maybe also TOP:<br/><br/>rule TOP { ^ [ &lt;statement&gt; || . { self.panic($/, &quot;Expected a <br/>statement&quot;) } ] $ };<br/><br/>That extra dot before the panic ensures it&#39;s not called at the end of <br/>the string. If you don&#39;t want that, you could also do<br/><br/>[ &lt;statement&gt; || $ || { self.panic(...) } ]<br/><br/>Cheers,<br/>Moritz<br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36615.html Wed, 11 May 2016 08:18:17 +0000 Re: Unwanted failure and FAILGOAL by Damian Conway Hi Richard,<br/><br/>Not a complete answer to your question;<br/>just an observation about your grammar:<br/><br/>&gt; rule TOP { ^ &lt;statement&gt;+ $ };<br/>&gt;<br/>&gt; rule statement { &lt;id&gt; &#39;=&#39; &lt;endvalue&gt;<br/>&gt; | { { self.panic($/, &quot;Declaration syntax incorrect&quot;) } }<br/>&gt; };<br/>&gt;<br/>&gt; rule endvalue { &lt;keyword&gt; &#39;(&#39; ~ &#39;)&#39; &lt;pairlist&gt;<br/>&gt; | { self.panic($/, &quot;Invalid declaration.&quot;) }<br/>&gt; }<br/><br/>That&#39;s more or less the equivalent of:<br/><br/> sub TOP {<br/> die if !at_start_of_input();<br/> loop { last unless try statement() };<br/> die if !at_end_of_input();<br/> }<br/><br/> sub statement {<br/> try { id(); match_literal(&#39;=&#39;); endvalue() }<br/> or<br/> die &quot;Declaration syntax incorrect&quot;;<br/> }<br/><br/> sub endvalue {<br/> try { keyword(); match_literal(&#39;(&#39;); pairlist();<br/>match_literal(&#39;)&#39;) }<br/> or<br/> die &quot;Invalid declaration.&quot;<br/> }<br/><br/>In which case, would you really have expected a call to TOP()<br/>NOT to throw an exception from statement(), the first time statement()<br/>couldn&#39;t match (as it inevitably won&#39;t if we&#39;re at the end of the input)???<br/><br/>If these were subroutines, I suspect you&#39;d have written something<br/>more like:<br/><br/> sub statement {<br/> try { id(); match_literal(&#39;=&#39;); endvalue() }<br/> or<br/><br/>* !at_end_of_input() &amp;&amp; die<br/>&quot;Declaration syntax incorrect&quot;*<br/> }<br/><br/> sub endvalue {<br/> try { keyword(); match_literal(&#39;(&#39;); pairlist();<br/>match_literal(&#39;)&#39; }<br/> or<br/><br/>* !at_end_of_input() &amp;&amp; die<br/>&quot;Invalid declaration.&quot;;*<br/> }<br/><br/>which, in a regex, would be something like:<br/><br/> rule TOP { ^ &lt;statement&gt;+ $ };<br/><br/> rule statement {<br/> &lt;id&gt; &#39;=&#39; &lt;endvalue&gt;<br/> |<br/>* \S **# ...means we found something else, so...*<br/>* { self.panic($/, &quot;Declaration syntax incorrect&quot;) }*<br/> };<br/><br/> rule endvalue {<br/> &lt;keyword&gt; &#39;(&#39; ~ &#39;)&#39; &lt;pairlist&gt;<br/> |<br/>* \S **# ...means we found something else, so...*<br/>* { self.panic($/, &quot;Invalid declaration.&quot;) }*<br/> }<br/><br/>Though, personally, I&#39;d have been inclined to write it like this:<br/><br/> rule TOP { ^ &lt;statement&gt;+ *[ $ | &lt;unexpected&gt; ]* }<br/><br/> rule statement { &#39;ID&#39; &#39;=&#39; &lt;endvalue&gt; }<br/><br/> rule endvalue { &#39;keyword&#39; &#39;(&#39; ~ &#39;)&#39; &#39;pairlist&#39; }<br/><br/><br/><br/>* rule unexpected { $&lt;unexpected&gt; = (\N+) {<br/>self.panic($/,&quot;Expected statement but found &#39;$&lt;unexpected&gt;&#39;&quot;)<br/>} }*<br/><br/>In other words: after the statements, we&#39;re either at the end of the input,<br/>or else we found something unexpected, so capture it and then report it.<br/><br/>HTH,<br/><br/>Damian http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36614.html Wed, 11 May 2016 07:20:49 +0000 Unwanted failure and FAILGOAL by Richard Hainsworth I have the following in a grammar<br/><br/> rule TOP { ^ &lt;statement&gt;+ $ };<br/><br/> rule statement { &lt;id&gt; &#39;=&#39; &lt;endvalue&gt;<br/> | { { self.panic($/, &quot;Declaration syntax <br/>incorrect&quot;) } }<br/> };<br/><br/> rule endvalue { &lt;keyword&gt; &#39;(&#39; ~ &#39;)&#39; &lt;pairlist&gt;<br/> | { self.panic($/, &quot;Invalid declaration.&quot;) }<br/> }<br/><br/>The grammar parses a correct input file up until the end of the file. At <br/>that point even if there is no un-consumed input, there is an attempt to <br/>match &lt;id&gt;, which fails. The failure causes the panic with &#39;Declaration <br/>syntax&#39;.<br/><br/>Am I missing something simple here?<br/><br/>I would have thought (though this is only a very newbie assumption) <br/>that if the end of the input being sent to the grammar has been reached <br/>after the last &lt;statement&gt; has been matched, then there should be no <br/>reason for the parse method to try to match &lt;statement&gt; again, and if it <br/>fails to test for the end of input.<br/><br/>Abstractly, it seems to me to be a bit like the difference between <br/>testing for the truth of a condition before entering a loop, and testing <br/>for the truth after the loop.<br/><br/>In trying to find a way out of this, I went looking for some information <br/>about FAILGOAL. I could not find anything in the documentation or in the <br/>specifications.<br/><br/>Google provided me with some conversations about FAILGOAL, but nothing <br/>about how to use it. I do not know enough about the guts of Rakudo to <br/>know where to look.<br/><br/>Would it be possible for someone who knows about this to add something <br/>to the Documentation on Grammars?<br/><br/>(As I write this, I thought may be I need a lookahead pattern in the <br/>TOP rule to ensure there is still input. But even so, that seems counter <br/>intuitive.)<br/><br/><br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36613.html Wed, 11 May 2016 05:45:33 +0000 [perl6/specs] 5ce9ca: Fix a site search function by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 5ce9cab30d605de628588a3d0559fe32164bd2d1<br/> https://github.com/perl6/specs/commit/5ce9cab30d605de628588a3d0559fe32164bd2d1<br/> Author: titsuki &lt;titsuki@cpan.org&gt;<br/> Date: 2016-05-04 (Wed, 04 May 2016)<br/><br/> Changed paths:<br/> M html/index.html<br/><br/> Log Message:<br/> -----------<br/> Fix a site search function<br/><br/><br/> Commit: 1c7f86efdd4ac7e0847450a02d3a2ad293fa2c26<br/> https://github.com/perl6/specs/commit/1c7f86efdd4ac7e0847450a02d3a2ad293fa2c26<br/> Author: titsuki &lt;titsuki@cpan.org&gt;<br/> Date: 2016-05-04 (Wed, 04 May 2016)<br/><br/> Changed paths:<br/> M html/index.html<br/><br/> Log Message:<br/> -----------<br/> Merge pull request #109 from titsuki/fix-sitesearch-function<br/><br/>Fix a site search function<br/><br/><br/>Compare: https://github.com/perl6/specs/compare/e094a61055fc...1c7f86efdd4a http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36612.html Tue, 03 May 2016 18:50:10 +0000 [perl6/specs] e094a6: Bring META format closer to reality by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: e094a61055fc3d597b9870328fe598687bd49c03<br/> https://github.com/perl6/specs/commit/e094a61055fc3d597b9870328fe598687bd49c03<br/> Author: Jonathan Stowe &lt;jns@gellyfish.co.uk&gt;<br/> Date: 2016-05-02 (Mon, 02 May 2016)<br/><br/> Changed paths:<br/> M S22-package-format.pod<br/><br/> Log Message:<br/> -----------<br/> Bring META format closer to reality<br/><br/> * resource has been implemented differently<br/> * version literals should omit &quot;v&quot;<br/> * use proper JSON bool<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/05/msg36611.html Mon, 02 May 2016 13:02:46 +0000 [perl6/specs] 7bc794: [S07] change .push example (which doesn'tfollow o... by GitHub Branch: refs/heads/master<br/> Home: https://github.com/perl6/specs<br/> Commit: 7bc794550740055287da15c81460c9d8eaabb51a<br/> https://github.com/perl6/specs/commit/7bc794550740055287da15c81460c9d8eaabb51a<br/> Author: David Warring &lt;david.warring@gmail.com&gt;<br/> Date: 2016-04-26 (Tue, 26 Apr 2016)<br/><br/> Changed paths:<br/> M S07-lists.pod<br/><br/> Log Message:<br/> -----------<br/> [S07] change .push example (which doesn&#39;t follow one-arg rule) to .append.<br/><br/>As discussed - closes #104<br/><br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/04/msg36610.html Tue, 26 Apr 2016 14:57:38 +0000 Announce: Rakudo Star Release 2016.04 by Steve Mynott # Announce: Rakudo Star Release 2016.04<br/><br/>## A useful and usable production distribution of Perl 6<br/><br/>On behalf of the Rakudo and Perl 6 development teams, I&#39;m honored to announce<br/>the April 2016 release of &quot;Rakudo Star&quot;, a useful and usable production<br/>distribution of Perl 6. The tarball for the April 2016 release is available<br/>from &lt;http://rakudo.org/downloads/star/&gt;.<br/><br/>This is the second post-Christmas (production) release of Rakudo Star and<br/>implements Perl v6.c. It comes with support for the MoarVM backend (all module<br/>tests pass on supported platforms).<br/><br/>Please note that this release of Rakudo Star is not fully functional with the<br/>JVM backend from the Rakudo compiler. Please use the MoarVM backend only.<br/><br/>In the Perl 6 world, we make a distinction between the language (&quot;Perl 6&quot;) and<br/>specific implementations of the language such as &quot;Rakudo Perl&quot;. This Star<br/>release includes [release 2016.04] of the [Rakudo Perl 6 compiler], version<br/>2016.04 of [MoarVM], plus various modules, documentation, and other resources<br/>collected from the Perl 6 community.<br/><br/>[release 2016.04]:<br/>https://raw.githubusercontent.com/rakudo/rakudo/2016.04/docs/announce/2016.04.md<br/>[Rakudo Perl 6 compiler]: http://github.com/rakudo/rakudo<br/>[MoarVM]: http://moarvm.org/<br/><br/>Some of the new compiler features since the last Rakudo Star release include:<br/><br/> * Much improved REPL with multi-line support.<br/> * Native string arrays.<br/> * Values in the environment value hash are now allomorphic.<br/> * Blob is now a proper value type.<br/> * Many Time &amp; Memory efficiency improvements including faster<br/>accessor/mutators, sorting and object comparison.<br/> * Can now uninstall modules.<br/> * Modules can now be shared between rakudo versions.<br/> * &quot;magic&quot; inc/dec cleaned up.<br/> * utf8-c8 encoding crashes fixed.<br/> * pre-comp locking fix.<br/> * missing module error mentions line number.<br/> * The usual assortment of bug fixes and error message improvements.<br/><br/>Notable changes in modules shipped with Rakudo Star:<br/><br/> * Bailador: removed and available in the ecosystem.<br/> * ufo: removed and available in the ecosystem.<br/> * Native::Resources: helper for native code added.<br/> * DBIish: Better Oracle &amp; Postgres support, more GLRish API and many<br/>other fixes.<br/> * Shell::Command: deprecated &quot;which&quot;.<br/> * Panda: Fix issues with paths containing spaces, &#39;--help&#39; option added etc.<br/> * p6doc: no longer creates empty FakeDir directories (was workaround<br/>for now fixed precomp bug).<br/> * JSON::Fast: fix for undefined value.<br/> * NativeHelpers::Blob: version 0.1.8 with improved windows tests.<br/> * PSGI: allow output to be a Buf.<br/> * Shell::Command: travis fix and deprecate which on Windows and Mac.<br/> * And much more.<br/><br/>There are some key features of Perl 6 that Rakudo Star does not yet<br/>handle appropriately, although they will appear in upcoming releases.<br/>Some of the not-quite-there features include:<br/><br/> * advanced macros<br/> * non-blocking I/O (in progress)<br/> * some bits of Synopsis 9 and 11<br/><br/>There is an online resource at &lt;http://perl6.org/compilers/features&gt;<br/>that lists the known implemented and missing features of Rakudo&#39;s<br/>backends and other Perl 6 implementations.<br/><br/>In many places we&#39;ve tried to make Rakudo smart enough to inform the<br/>programmer that a given feature isn&#39;t implemented, but there are many<br/>that we&#39;ve missed. Bug reports about missing and broken features are<br/>welcomed at &lt;rakudobug@perl.org&gt;.<br/><br/>See &lt;http://perl6.org/&gt; for links to much more information about<br/>Perl 6, including documentation, example code, tutorials, presentations,<br/>reference materials, design documents, and other supporting resources.<br/>Some Perl 6 tutorials are available under the &quot;docs&quot; directory in<br/>the release tarball.<br/><br/>The development team thanks all of the contributors and sponsors for<br/>making Rakudo Star possible. If you would like to contribute, see<br/>&lt;http://rakudo.org/how-to-help&gt;, ask on the &lt;perl6-compiler@perl.org&gt;<br/>mailing list, or join us on IRC \#perl6 on freenode.<br/><br/><br/>-- <br/>4096R/EA75174B Steve Mynott &lt;steve.mynott@gmail.com&gt;<br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/04/msg36609.html Mon, 25 Apr 2016 23:42:52 +0000 [perl6/specs] 73f566: [S11] Typo fix by GitHub Branch: refs/heads/master <br/> Home: https://github.com/perl6/specs <br/> Commit: 73f566e8f65381f3d324c85dd0a79b9961bf8ed4 <br/> https://github.com/perl6/specs/commit/73f566e8f65381f3d324c85dd0a79b9961bf8ed4 <br/> Author: Tadeusz So&#x15B;nierz &lt;tadeusz.sosnierz@onet.pl&gt; <br/> Date: 2016-04-21 (Thu, 21 Apr 2016) <br/> <br/> Changed paths: <br/> M S11-modules.pod <br/> <br/> Log Message: <br/> ----------- <br/> [S11] Typo fix <br/> <br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/04/msg36608.html Fri, 22 Apr 2016 11:02:22 +0000 Announce: [SixFix] A weekly dose of Perl 6 delivered to your inbox by Nigel Hamilton SixFix is a weekly email with something new to learn about Perl 6. But there&#39;s<br/>a catch! Each email includes a coding challenge and a question about Perl 6<br/>you must answer to receive your next SixFix.<br/><br/>SixFix helps you learn Perl 6 with practical coding exercises (approx 1/2<br/>an hour each week). You will write Perl 6 code that helps you code. The<br/>first SixFix course is free and is delivered in 7 weekly doses.<br/><br/>Sign up for your first SixFix here:<br/><br/>http://sixfix.nigelhamilton.com http://www.nntp.perl.org/group/perl.perl6.language/2016/04/msg36607.html Tue, 19 Apr 2016 05:37:04 +0000 Re: A practical benchmark shows speed challenges for Perl 6 by yary On Wed, Mar 30, 2016 at 3:20 PM, Elizabeth Mattijsen &lt;liz@dijkmat.nl&gt; wrote: <br/>&gt; Thanks for your thoughts! <br/>&gt; <br/>&gt; I&rsquo;ve implemented $*DEFAULT-READ-ELEMS in https://github.com/rakudo/rakudo/commit/5bd1e . <br/>&gt; <br/>&gt; Of course, all of this is provisional, and open for debate and bikeshedding. <br/> <br/> <br/>Thanks! And that was fast! <br/> <br/>Allowing DEFAULT-READ-ELEMS to be set from the environment&#39;s a good <br/>idea that I hadn&#39;t thought of- since it is a machine-dependent <br/>performance tweak, letting it be set outside the code is a good idea. <br/> <br/>I had originally envisioned this as an &quot;option&quot; to &quot;sub open&quot; for <br/>fine-grained control as to which IO::Handles got what <br/>DEFAULT-READ-ELEMS, but I&#39;m not sure it belongs there. After all it is <br/>a performance-related tweak and I&#39;m liking the idea of it being <br/>primarily set from the environment; setting it in the code means <br/>you&#39;re writing something for a particular host, don&#39;t need to change <br/>the spec to support that. <br/> <br/>Is there anything similar on the &quot;write&quot; side- output buffering- that <br/>could use this treatment? <br/> <br/>-y <br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/03/msg36606.html Wed, 30 Mar 2016 20:11:33 +0000 Re: A practical benchmark shows speed challenges for Perl 6 by Elizabeth Mattijsen &gt; On 30 Mar 2016, at 16:06, yary &lt;not.com@gmail.com&gt; wrote: <br/>&gt; <br/>&gt; Cross-posting to the compiler group- <br/>&gt; <br/>&gt; On Wed, Mar 30, 2016 at 8:10 AM, Elizabeth Mattijsen &lt;liz@dijkmat.nl&gt; wrote: <br/>&gt;&gt; If you know the line endings of the file, using IO::Handle.split($line-ending) (note the actual character, rather than a regular expression) might help. That will read in the file in chunks of 64K and then lazily serve lines from that chunk. <br/>&gt; <br/>&gt; This reminds me of a pet peeve I had with p5: Inability to easily <br/>&gt; change the default buffer size for reading &amp; writing. <br/>&gt; <br/>&gt; I&#39;m the lone Perl expert at $work and at one point was trying to keep <br/>&gt; a file processing step in perl. These files were about 100x the size <br/>&gt; of the server&#39;s RAM, consisted of variable-length newline-terminated <br/>&gt; text, the processing was very light, there would be a few running in <br/>&gt; parallel. The candidate language, C#, has a text-file-reading object <br/>&gt; that lets you set its read-ahead buffer on creation/opening the file- <br/>&gt; can&#39;t remember the details. That size had a large impact on the <br/>&gt; performance of this task. With perl... I could not use the <br/>&gt; not-so-well-documented IO::Handle-&gt;setvbuf because my OS didn&#39;t <br/>&gt; support it. I did hack together something with sysread, but C# won in <br/>&gt; the end due partly to that. <br/>&gt; <br/>&gt; It seems this &quot;hiding-of-buffer&quot; sub-optimal situation is being <br/>&gt; repeated in Perl6: neither https://doc.perl6.org/routine/open nor <br/>&gt; http://doc.perl6.org/type/IO::Handle mention a buffer, yet IO::Handle <br/>&gt; reads ahead and buffers. Experience shows that being able to adjust <br/>&gt; this buffer can help in certain situations. Also consider that perl5 <br/>&gt; has defaulted to 4k and 8k, whereas perl6 is apparently using 64k, as <br/>&gt; evidence that this buffer needs to change as system builds evolve. <br/>&gt; <br/>&gt; Please make this easily readable &amp; settable, anywhere it&#39;s implemented! <br/> <br/>Thanks for your thoughts! <br/> <br/>I&rsquo;ve implemented $*DEFAULT-READ-ELEMS in https://github.com/rakudo/rakudo/commit/5bd1e . <br/> <br/>Of course, all of this is provisional, and open for debate and bikeshedding. <br/> <br/> <br/>Liz http://www.nntp.perl.org/group/perl.perl6.language/2016/03/msg36605.html Wed, 30 Mar 2016 19:20:49 +0000 Re: A practical benchmark shows speed challenges for Perl 6 by yary Cross-posting to the compiler group-<br/><br/>On Wed, Mar 30, 2016 at 8:10 AM, Elizabeth Mattijsen &lt;liz@dijkmat.nl&gt; wrote:<br/>&gt; If you know the line endings of the file, using IO::Handle.split($line-ending) (note the actual character, rather than a regular expression) might help. That will read in the file in chunks of 64K and then lazily serve lines from that chunk.<br/><br/>This reminds me of a pet peeve I had with p5: Inability to easily<br/>change the default buffer size for reading &amp; writing.<br/><br/>I&#39;m the lone Perl expert at $work and at one point was trying to keep<br/>a file processing step in perl. These files were about 100x the size<br/>of the server&#39;s RAM, consisted of variable-length newline-terminated<br/>text, the processing was very light, there would be a few running in<br/>parallel. The candidate language, C#, has a text-file-reading object<br/>that lets you set its read-ahead buffer on creation/opening the file-<br/>can&#39;t remember the details. That size had a large impact on the<br/>performance of this task. With perl... I could not use the<br/>not-so-well-documented IO::Handle-&gt;setvbuf because my OS didn&#39;t<br/>support it. I did hack together something with sysread, but C# won in<br/>the end due partly to that.<br/><br/>It seems this &quot;hiding-of-buffer&quot; sub-optimal situation is being<br/>repeated in Perl6: neither https://doc.perl6.org/routine/open nor<br/>http://doc.perl6.org/type/IO::Handle mention a buffer, yet IO::Handle<br/>reads ahead and buffers. Experience shows that being able to adjust<br/>this buffer can help in certain situations. Also consider that perl5<br/>has defaulted to 4k and 8k, whereas perl6 is apparently using 64k, as<br/>evidence that this buffer needs to change as system builds evolve.<br/><br/>Please make this easily readable &amp; settable, anywhere it&#39;s implemented!<br/><br/><br/>-y<br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/03/msg36604.html Wed, 30 Mar 2016 14:07:30 +0000 [perl6/specs] bd4686: unmanaged size. jnthn++ by GitHub Branch: refs/heads/master <br/> Home: https://github.com/perl6/specs <br/> Commit: bd468647d355eb6f50524426615bbc6ea9bc3c78 <br/> https://github.com/perl6/specs/commit/bd468647d355eb6f50524426615bbc6ea9bc3c78 <br/> Author: St&eacute;phane Payrard &lt;cognominal@gmail.com&gt; <br/> Date: 2016-03-24 (Thu, 24 Mar 2016) <br/> <br/> Changed paths: <br/> M S99-glossary.pod <br/> <br/> Log Message: <br/> ----------- <br/> unmanaged size. jnthn++ <br/> <br/> http://www.nntp.perl.org/group/perl.perl6.language/2016/03/msg36603.html Fri, 25 Mar 2016 12:24:10 +0000