Re: Announce: Rakudo Star Release 2017.07
On 07/25/2017 12:30 AM, Elizabeth Mattijsen wrote: What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler release with a set of useful modules added (“batteries included”). https://rakudo.perl6.org/downloads/star/ vs https://rakudo.perl6.org/downloads/rakudo/ And to add insult Fedora only supports Rakudo
Re: Is win 32 being worked on?
On 21 July 2017 at 09:07, Mark Carterwrote: > I noticed that there is no Windows 32-bit version of rakudo, and it won't > even compile on cygwin. Returning the thread to the original topic of Rakudo (not Star) http://rakudo.org/how-to-get-rakudo/#Installing-Rakudo-Star-Cygwin explains why Rakudo doesn't compile on Cygwin ( both 32 bit and 64 bit) since pthread_barrier isn't available on cygwin. There is a fork of cygwin called mingw which works (since it doesn't pretend to be POSIX). This is bundled with Strawberry Perl which is convenient since you only have to install one tool rather than two. 32 bit Windows should compile Rakudo if you install Strawberry Perl and have both gcc and gmake in the path. Note you need to use cmd.exe as a shell (not bash) and gmake rather than Window's usual nmake. -- 4096R/EA75174B Steve Mynott
Re: Fwd: Re: Is win 32 being worked on?
On Tue, Jul 25, 2017 at 5:41 PM, Darren Duncanwrote: > On 2017-07-25 2:08 PM, Steve Mynott wrote: > >> To clarify Rakudo itself *should* compile on 32 bit Windows systems >> (using either MSVC or mingw and maybe cygwin). >> >> The problem with Rakudo Star is that some of the C based modules >> probably don't work. >> > > So is it feasible to remove those modules from Rakudo Star? > Linenoise makes the REPL a lot more usable, and is generally easier to get online on Windows than readline. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
Re: Fwd: Re: Is win 32 being worked on?
On 2017-07-25 2:08 PM, Steve Mynott wrote: To clarify Rakudo itself *should* compile on 32 bit Windows systems (using either MSVC or mingw and maybe cygwin). The problem with Rakudo Star is that some of the C based modules probably don't work. So is it feasible to remove those modules from Rakudo Star? What manner of functionality are they? Would their lack be a problem for most people? It seems to me that one of these things should happen: 1. Modules that don't work with all platforms normally supported by a Rakudo Star distribution get dropped from Rakudo Star. 2. Win32 is dropped from the main list of Rakudo Star distributions. 3. The problematic modules are expressly excluded from the Win32 distros, and this fact is documented, while there can otherwise be up to date Win32 distros with the core and all other features besides these modules. If the modules you describe are considered essential, they should receive updates to run with Win32; otherwise they should be dropped from Star as they are clearly not considered that essential. Dropped modules can still be installed separately as add-ons where they work. -- Darren Duncan
Re: Fwd: Re: Is win 32 being worked on?
To clarify Rakudo itself *should* compile on 32 bit Windows systems (using either MSVC or mingw and maybe cygwin). The problem with Rakudo Star is that some of the C based modules probably don't work. S On 25 July 2017 at 20:46, Brandon Allberywrote: > On Tue, Jul 25, 2017 at 3:37 PM, Mark Carter wrote: >> >> On 25/07/2017 20:31, Darren Duncan wrote: >>> >>> I would question why any desktop computer manufacturers were still even >>> shipping non-64-bit capable hardware in 2010. >> >> I dual-boot (rarely) with it, and it runs 64-bit Ubuntu. I am using a >> Dell, which came with 32-bit Win 7. > > > For quite a long time, the "common wisdom" was that 64 bit was a waste of > memory on smaller machines and caused compatibility problems, so > 64-bit-capable hardware running 32-bit OSes was quite common. > > (For Windows the latter is actually true, insofar as 64 bit processes can't > load 32 bit DLLs and 32 bit programs are actually run in a minimal > hypervisor on Win10. This was less well developed when Win7 was current; the > hypervisor only ran WinXP iirc, not 32 bit W7.) > > -- > brandon s allbery kf8nh sine nomine associates > allber...@gmail.com ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net -- 4096R/EA75174B Steve Mynott
Re: Fwd: Re: Is win 32 being worked on?
On Tue, Jul 25, 2017 at 3:37 PM, Mark Carterwrote: > On 25/07/2017 20:31, Darren Duncan wrote: > >> I would question why any desktop computer manufacturers were still even >> shipping non-64-bit capable hardware in 2010. >> > I dual-boot (rarely) with it, and it runs 64-bit Ubuntu. I am using a > Dell, which came with 32-bit Win 7. > For quite a long time, the "common wisdom" was that 64 bit was a waste of memory on smaller machines and caused compatibility problems, so 64-bit-capable hardware running 32-bit OSes was quite common. (For Windows the latter is actually true, insofar as 64 bit processes can't load 32 bit DLLs and 32 bit programs are actually run in a minimal hypervisor on Win10. This was less well developed when Win7 was current; the hypervisor only ran WinXP iirc, not 32 bit W7.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
Re: Fwd: Re: Is win 32 being worked on?
On 25/07/2017 20:31, Darren Duncan wrote: I would question why any desktop computer manufacturers were still even shipping non-64-bit capable hardware in 2010. I dual-boot (rarely) with it, and it runs 64-bit Ubuntu. I am using a Dell, which came with 32-bit Win 7.
Re: Fwd: Re: Is win 32 being worked on?
I would question why any desktop computer manufacturers were still even shipping non-64-bit capable hardware in 2010. Apple Macintoshes were 64 bit Intel across the board in 2006, or 11 years ago. People like to accuse Apple of being constantly behind the curve on hardware compared to other PC makers, and yet other makers were shipping 32 bit only still 4 years after Apple stopped? -- Darren Duncan On 2017-07-25 12:16 PM, Mark Carter wrote: On 2017-07-25 11:05 AM, Mark Carter wrote: On 25/07/2017 18:34, Darren Duncan wrote: How often would someone reasonably be using a cutting edge tool like Rakudo on Windows without having a 64 bit Windows these days? Thing is, I have a computer from 2010, Win 7 32-bit. It's fast enough for me, and does what I want it to do. I'm not going to spend money just to run Perl6. It doesn't even compile on cygwin. Python is available in 32-bit. Why not perl6?
Fwd: Re: Is win 32 being worked on?
On 2017-07-25 11:05 AM, Mark Carter wrote: On 25/07/2017 18:34, Darren Duncan wrote: How often would someone reasonably be using a cutting edge tool like Rakudo on Windows without having a 64 bit Windows these days? Thing is, I have a computer from 2010, Win 7 32-bit. It's fast enough for me, and does what I want it to do. I'm not going to spend money just to run Perl6. It doesn't even compile on cygwin. Python is available in 32-bit. Why not perl6?
Re: Announce: Rakudo Star Release 2017.07
TL;DR Imo, one of Perl 6's notable strengths is its approach to its specification. Imo companies will love it. I can see it becoming a primary tool for driving P6 forward in just the right way. Steve has already answered with the short version of some of what I say below, and I agree with what you (Darren) said in your reply to him. So perhaps this is more for ToddAndMargo or other readers. >From the start in 2000, Larry intended that the P6 project would distinguish between various distinct notions of "specification": * An evolving set of English documents that would be used to guide compiler developers attempting to write a compiler that implements that "specification". For the last few years P6 project leaders have been calling these "Design Documents". The latest/last versions of these are stored at design.perl6.org. They are now largely an historical footnote -- calling these or any other English language documents a "specification" was explicitly deprecated some years ago. * An evolving set of English documents that would be used to guide end users attempting to understand or write P6 code. Aka end user documentation. The latest version of this is stored at doc.perl6.org. Contributors can draw insight from the design documents (as per previous bullet point) but are supposed to focus on the only remaining specification (as per the next bullet point). * An evolving Executable specification that emerges from that effort. A compiler **must** match **100%** of this executable specification if the compiler is to be officially allowed to claim it implements that specification. This is what the 6.c specification is and what the 6.d specification will be. * The 6.c specification is stored at https://github.com/perl6/roast/tree/6.c (Maybe we should change the description from "Perl 6 test suite" to "Perl 6 language specification".) There's also a 6.c errata at https://github.com/perl6/roast/tree/6.c-errata which, aiui, is what the monthly Rakudo releases target. So, anything you read in English, like "doesn't yet implement macros" is... written in English and is not part of a Perl 6 language specification, per contemporary P6 usage of the word "specification". > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. Aiui Rakudo's HEAD implemented all of 6.c (on at least one platform) as of December 25th 2015 and each subsequent monthly release has as well. (Well, actually, all of 6.c.errata.) In principle this is an excellent foundation for manageable (in tech and business senses), systematic, community driven, compiler dev mediated, language stability, backwards compatibility, and evolution. If someone (or some company) wants to drive the language forward, then they work with the community to propose changes to the test suite for 6.d or some later 6.* version. These changes test that the particular features they want are working. Community members can do things like attaching a time-limited incentive for compiler devs to alter the compiler to pass some particular set of new tests. Indeed, I imagine it would be fairly easy to set up a flow of direct micro-funding of whatever a given community participant considers more important to them. If it's backwards compatibility, then write tests that ensure that backwards compatibility if they haven't already been written and/or add incentives to currently failing/skipped tests. A similar approach applies for those wanting more test coverage of existing features, or new features. -- raiph On Tue, Jul 25, 2017 at 11:23 AM, Darren Duncanwrote: > There's a key difference however. > > While programming languages continue to evolve, the expectation is that a > production-complete Rakudo would always be a functional superset (or equal > to) the Perl 6 language specification which is current at the time. > > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. > > The original question would be more accurately phrased, "Any idea when > Rakudo will release implementing the full Perl 6.c?" > > -- Darren Duncan > > On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote: >> >> If that is the question, the answer is: the junction of “never" and “now". >> Which would also be the answer for Pumpking Perl 5, or any other programming >> language like ever. Because as long as people are using it, a programming >> language will evolve. Much like any human endeavour I would say. >> >>> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick wrote: >>> >>> I assume the meaning is, roughly when is the implementation expected >>> to cover the entire spec? >>> >>> Answering this is probably an exercise in
Re: Is win 32 being worked on?
I recommend removing the reference/link to the Rakudo Star 32 bit Windows installer from http://rakudo.org/how-to-get-rakudo/ and leave only platforms that are reasonably up to date. The old 32 bit Windows installers can still be in the archives of course, but grouping it with the other installers that are 1.5 years newer and gaining isn't doing anyone any favors. The highlighted ones should be in sync on functionality. This link could return if the 32 bit Windows catches up. How often would someone reasonably be using a cutting edge tool like Rakudo on Windows without having a 64 bit Windows these days? -- Darren Duncan On 2017-07-23 10:29 AM, Steve Mynott wrote: Rakudo itself probably does compile on Windows 32-bit (or least it did last time I tried it). But here is no Rakudo Star 32 bit MSI due to problems with modules not working -- I think linenoise failed to compile last time I tried it (and I believe it only works under GCC not MSVC on 64 bit). I'm afraid there is a lot of bitrot with modules not working under Windows I'm afraid in general (both 64 bit and 32 bit). We really need a volunteer Windows programmer to take a look at things since most of us run under various UNIX type OSes regularly rather than Windows. S On 21 July 2017 at 10:37, Todd Chesterwrote: On 07/21/2017 01:57 AM, Mark Carter wrote: On 21/07/2017 09:50, Todd Chester wrote: I may be wrong, but I do believe what you want is called "Rakudo Star". You can download it from https://rakudo.perl6.org/downloads/star/ But no recent win 32-bit. https://rakudo.perl6.org/downloads/star/rakudo-star-2016.01-x86%20(no%20JIT).msi seems to be the last one
Re: Announce: Rakudo Star Release 2017.07
On 2017-07-25 10:05 AM, Brandon Allbery wrote: On Tue, Jul 25, 2017 at 11:45 AM, Darren Duncan wrote: However I assume it is the 3 bullet points that the release announcement highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11. The fact the announcement highlights these implies they are part of the creators' definition of "complete". The "advanced macros" part, at least, probably needs to go away: a large part of the problem is that nobody actually knows what "advanced macros" for Perl 6 should do, or even look like. (See for example masak's 007, which is a playground for macros to try to get a handle on the question of what they ought to be/do.) I agree with your point and should further say that I think at this point the Rakudo announcements should stop naming that features are missing except where they are key show-stopper-for-some features. Don't highlight the fact that some things are missing. That would always be the case. At this point things are complete enough that most people wouldn't even notice things were missing if they weren't told and it doesn't affect them. In my opinion, non-blocking I/O is the only thing on the list that deserves to be highlighted, that and the warnings about the level of JVM support. -- Darren Duncan
Re: Announce: Rakudo Star Release 2017.07
On Tue, Jul 25, 2017 at 11:45 AM, Darren Duncanwrote: > However I assume it is the 3 bullet points that the release announcement > highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11. > The fact the announcement highlights these implies they are part of the > creators' definition of "complete". The "advanced macros" part, at least, probably needs to go away: a large part of the problem is that nobody actually knows what "advanced macros" for Perl 6 should do, or even look like. (See for example masak's 007, which is a playground for macros to try to get a handle on the question of what they ought to be/do.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
Re: Announce: Rakudo Star Release 2017.07
On 2017-07-25 8:32 AM, Steve Mynott wrote: On 25 July 2017 at 16:23, Darren Duncanwrote: There's a key difference however. While programming languages continue to evolve, the expectation is that a production-complete Rakudo would always be a functional superset (or equal to) the Perl 6 language specification which is current at the time. The Perl 6 language specification is the test suite. So if the test suite passes then it's complete! Which is of course a tautology. So by that definition, "complete" is that the arbitrary subset of the spec that an implementation chooses to do passes the tests for those parts, and the rest of the tests skip rather than fail. So I think it is reasonable for Rakudo to actually implement ALL of 6.c before too long, that it would catch up, and otherwise the intent is that Rakudo would be leading on things that eventually become 6.d etc later. Which missing parts are you concerned about? I'm not personally concerned about any parts at this time. It is ToddAndMargo that is concerned about it, who asked the question. However I assume it is the 3 bullet points that the release announcement highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11. The fact the announcement highlights these implies they are part of the creators' definition of "complete". -- Darren Duncan
Re: Announce: Rakudo Star Release 2017.07
On 25 July 2017 at 16:33, Stephen Wilcoxonwrote: > I don't see anything in the notes (though I may have missed it) about JVM. > I thought the plan was to get JVM functional again (though likely still > lagging MoarVM feature support) with the 2017.07 release? There are comments in the README "Please note that this release of Rakudo Star is *not* fully functional with the JVM backend from the Rakudo compiler. Use the JVM backend only if you are trying to help with fixing JVM support (which is best done upstream with the monthly Rakudo release). This is a known issue and it's not worth reporting JVM failures as bugs unless you have patches." The last time I tried it (and this was a while ago) I was able to build with JVM and run simple (dozen line) programs OK. But complex programs like zef didn't work and so installing modules wasn't possible. S
Re: Announce: Rakudo Star Release 2017.07
I don't see anything in the notes (though I may have missed it) about JVM. I thought the plan was to get JVM functional again (though likely still lagging MoarVM feature support) with the 2017.07 release? Perl 6 on MoarVM is definitely interesting but, to me at least, the single biggest practical impact or Rakudo was that it is (or was) supposed to run on JVM (allowing usage of any other libs on JVM and, probably more importantly, making it easier to convince management to allow using it). On Tue, Jul 25, 2017 at 10:23 AM, Darren Duncanwrote: > There's a key difference however. > > While programming languages continue to evolve, the expectation is that a > production-complete Rakudo would always be a functional superset (or equal > to) the Perl 6 language specification which is current at the time. > > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. > > The original question would be more accurately phrased, "Any idea when > Rakudo will release implementing the full Perl 6.c?" > > -- Darren Duncan > > On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote: > >> If that is the question, the answer is: the junction of “never" and >> “now". Which would also be the answer for Pumpking Perl 5, or any other >> programming language like ever. Because as long as people are using it, a >> programming language will evolve. Much like any human endeavour I would >> say. >> >> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick wrote: >>> >>> I assume the meaning is, roughly when is the implementation expected >>> to cover the entire spec? >>> >>> Answering this is probably an exercise in futility, because its up to >>> the community and not anyone in particular. >>> >>> On 25 July 2017 at 17:00, Elizabeth Mattijsen wrote: >>> >> [snip] > > > > Any idea when the full Rakudo will be released? > What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler release with a set of useful modules added (“batteries included”). So you could argue that Rakudo doesn’t get fuller than with Rakudo Star! >>> >>
Re: Announce: Rakudo Star Release 2017.07
On 25 July 2017 at 16:23, Darren Duncanwrote: > There's a key difference however. > > While programming languages continue to evolve, the expectation is that a > production-complete Rakudo would always be a functional superset (or equal > to) the Perl 6 language specification which is current at the time. The Perl 6 language specification is the test suite. So if the test suite passes then it's complete! Which is of course a tautology. > So I think it is reasonable for Rakudo to actually implement ALL of 6.c > before too long, that it would catch up, and otherwise the intent is that > Rakudo would be leading on things that eventually become 6.d etc later. Which missing parts are you concerned about? > The original question would be more accurately phrased, "Any idea when > Rakudo will release implementing the full Perl 6.c?" It's a volunteer effort so this happens whenever someone who cares enough about missing parts and who has the time and skills to implement does it. S
Re: Announce: Rakudo Star Release 2017.07
There's a key difference however. While programming languages continue to evolve, the expectation is that a production-complete Rakudo would always be a functional superset (or equal to) the Perl 6 language specification which is current at the time. So I think it is reasonable for Rakudo to actually implement ALL of 6.c before too long, that it would catch up, and otherwise the intent is that Rakudo would be leading on things that eventually become 6.d etc later. The original question would be more accurately phrased, "Any idea when Rakudo will release implementing the full Perl 6.c?" -- Darren Duncan On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote: If that is the question, the answer is: the junction of “never" and “now". Which would also be the answer for Pumpking Perl 5, or any other programming language like ever. Because as long as people are using it, a programming language will evolve. Much like any human endeavour I would say. On 25 Jul 2017, at 09:42, Andrew Kirkpatrickwrote: I assume the meaning is, roughly when is the implementation expected to cover the entire spec? Answering this is probably an exercise in futility, because its up to the community and not anyone in particular. On 25 July 2017 at 17:00, Elizabeth Mattijsen wrote: [snip] Any idea when the full Rakudo will be released? What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler release with a set of useful modules added (“batteries included”). So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
Were there any failures before the "Building NQP ..." step? Somehow the moarvm that's packaged with the rakudo star didn't end up getting installed into your .local/bin, so you're getting the previous version, which - unsurprisingly - isn't new enough for current NQP and Rakudo.
Re: Announce: Rakudo Star Release 2017.07
Attempted build on Arch Linux: perl Configure.pl --prefix=$HOME/.local --backend=moar --gen-moar --gen-moar Resulting in: Building NQP ... /usr/bin/perl Configure.pl --prefix=/home/mcarter/.local --backends=moar --make-install Creating tools/build/install-jvm-runner.pl ... ===SORRY!=== Found /home/mcarter/.local/bin/moar version 2017.04-53-g66c6dda, which is too old. Wanted at least 2017.07 No suitable MoarVM (moar executable) found using the --prefix (You can get a MoarVM built automatically with --gen-moar.) Command failed (status 65280): /usr/bin/perl Configure.pl --prefix=/home/mcarter/.local --backends=moar --make-install
Re: Announce: Rakudo Star Release 2017.07
If that is the question, the answer is: the junction of “never" and “now". Which would also be the answer for Pumpking Perl 5, or any other programming language like ever. Because as long as people are using it, a programming language will evolve. Much like any human endeavour I would say. > On 25 Jul 2017, at 09:42, Andrew Kirkpatrickwrote: > > I assume the meaning is, roughly when is the implementation expected > to cover the entire spec? > > Answering this is probably an exercise in futility, because its up to > the community and not anyone in particular. > > On 25 July 2017 at 17:00, Elizabeth Mattijsen wrote: >>> On 25 Jul 2017, at 05:57, ToddAndMargo wrote: >>> On 07/24/2017 11:40 AM, Steve Mynott wrote: A useful and usable production distribution of Perl 6 On behalf of the Rakudo and Perl 6 development teams, I'm pleased to announce the July 2017 release of "Rakudo Star", a useful and usable production distribution of Perl 6. The tarball for the July 2017 release is available from https://rakudo.perl6.org/downloads/star/. Binaries for macOS and Windows (64 bit) are also available. This is the eighth post-Christmas (production) release of Rakudo Star and implements Perl v6.c. It comes with support for the MoarVM backend (all module tests pass on supported platforms). IMPORTANT: "panda" is to be removed very shortly since it is deprecated. Please use "zef" instead. Currently, Star is on a quarterly release cycle and 2017.10 (October) will follow later this year. Please note that this release of Rakudo Star is not fully functional with the JVM backend from the Rakudo compiler. Please use the MoarVM backend only. In the Perl 6 world, we make a distinction between the language ("Perl 6") and specific implementations of the language such as "Rakudo Perl". This Star release includes release 2017.07 of the Rakudo Perl 6 compiler, version 2017.07 MoarVM, plus various modules, documentation, and other resources collected from the Perl 6 community. Note this Star release contains NQP version 2017.07-9-gc0abee7 rather than the release NQP 2017.07 in order to fix the --ll-exception command line flag. The Rakudo compiler changes since the last Rakudo Star release of 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md" under the "rakudo/docs/announce" directory of the source distribution. Notable changes in modules shipped with Rakudo Star: + DBIish: Doc and CI updates + doc: Too many to list. p6doc fixed. + grammar-debugger: Works again now. + p6-io-string: New dep for doc. + p6-native-resources: Removed since deprecated and not used by linenoise. + panda: Officially deprecate panda in favour of zef. + perl6-Test-When: New dep for perl6-pod-to-bigpage. + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor. + tap-harness6: Replaces deprecated tap-harness6-prove6. + zef: Too many to list. There are some key features of Perl 6 that Rakudo Star does not yet handle appropriately, although they will appear in upcoming releases. Some of the not-quite-there features include: + advanced macros + non-blocking I/O (in progress) + some bits of Synopsis 9 and 11 There is an online resource at http://perl6.org/compilers/features that lists the known implemented and missing features of Rakudo's backends and other Perl 6 implementations. In many places we've tried to make Rakudo smart enough to inform the programmer that a given feature isn't implemented, but there are many that we've missed. Bug reports about missing and broken features are welcomed at rakudo...@perl.org. See https://perl6.org/ for links to much more information about Perl 6, including documentation, example code, tutorials, presentations, reference materials, design documents, and other supporting resources. Some Perl 6 tutorials are available under the "docs" directory in the release tarball. The development team thanks all of the contributors and sponsors for making Rakudo Star possible. If you would like to contribute, see http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org mailing list, or join us on IRC #perl6 on freenode. >>> >>> >>> Any idea when the full Rakudo will be released? >> >> What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler >> release with a set of useful modules added (“batteries included”). >> >> So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
I assume the meaning is, roughly when is the implementation expected to cover the entire spec? Answering this is probably an exercise in futility, because its up to the community and not anyone in particular. On 25 July 2017 at 17:00, Elizabeth Mattijsenwrote: >> On 25 Jul 2017, at 05:57, ToddAndMargo wrote: >> On 07/24/2017 11:40 AM, Steve Mynott wrote: >>> A useful and usable production distribution of Perl 6 >>> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to >>> announce the July 2017 release of "Rakudo Star", a useful and usable >>> production distribution of Perl 6. The tarball for the July 2017 >>> release is available from https://rakudo.perl6.org/downloads/star/. >>> Binaries for macOS and Windows (64 bit) are also available. >>> This is the eighth post-Christmas (production) release of Rakudo Star >>> and implements Perl v6.c. It comes with support for the MoarVM backend >>> (all module tests pass on supported platforms). >>> IMPORTANT: "panda" is to be removed very shortly since it is >>> deprecated. Please use "zef" instead. >>> Currently, Star is on a quarterly release cycle and 2017.10 (October) >>> will follow later this year. >>> Please note that this release of Rakudo Star is not fully functional >>> with the JVM backend from the Rakudo compiler. Please use the MoarVM >>> backend only. >>> In the Perl 6 world, we make a distinction between the language ("Perl >>> 6") and specific implementations of the language such as "Rakudo >>> Perl". >>> This Star release includes release 2017.07 of the Rakudo Perl 6 >>> compiler, version 2017.07 MoarVM, plus various modules, documentation, >>> and other resources collected from the Perl 6 community. >>> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather >>> than the release NQP 2017.07 in order to fix the --ll-exception >>> command line flag. >>> The Rakudo compiler changes since the last Rakudo Star release of >>> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md" >>> under the "rakudo/docs/announce" directory of the source distribution. >>> Notable changes in modules shipped with Rakudo Star: >>> + DBIish: Doc and CI updates >>> + doc: Too many to list. p6doc fixed. >>> + grammar-debugger: Works again now. >>> + p6-io-string: New dep for doc. >>> + p6-native-resources: Removed since deprecated and not used by linenoise. >>> + panda: Officially deprecate panda in favour of zef. >>> + perl6-Test-When: New dep for perl6-pod-to-bigpage. >>> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor. >>> + tap-harness6: Replaces deprecated tap-harness6-prove6. >>> + zef: Too many to list. >>> There are some key features of Perl 6 that Rakudo Star does not yet >>> handle appropriately, although they will appear in upcoming releases. >>> Some of the not-quite-there features include: >>> + advanced macros >>> + non-blocking I/O (in progress) >>> + some bits of Synopsis 9 and 11 >>> There is an online resource at http://perl6.org/compilers/features >>> that lists the known implemented and missing features of Rakudo's >>> backends and other Perl 6 implementations. >>> In many places we've tried to make Rakudo smart enough to inform the >>> programmer that a given feature isn't implemented, but there are many >>> that we've missed. Bug reports about missing and broken features are >>> welcomed at rakudo...@perl.org. >>> See https://perl6.org/ for links to much more information about Perl >>> 6, including documentation, example code, tutorials, presentations, >>> reference materials, design documents, and other supporting resources. >>> Some Perl 6 tutorials are available under the "docs" directory in the >>> release tarball. >>> The development team thanks all of the contributors and sponsors for >>> making Rakudo Star possible. If you would like to contribute, see >>> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org >>> mailing list, or join us on IRC #perl6 on freenode. >> >> >> Any idea when the full Rakudo will be released? > > What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler > release with a set of useful modules added (“batteries included”). > > So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!
Re: Announce: Rakudo Star Release 2017.07
> On 25 Jul 2017, at 05:57, ToddAndMargowrote: > On 07/24/2017 11:40 AM, Steve Mynott wrote: >> A useful and usable production distribution of Perl 6 >> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to >> announce the July 2017 release of "Rakudo Star", a useful and usable >> production distribution of Perl 6. The tarball for the July 2017 >> release is available from https://rakudo.perl6.org/downloads/star/. >> Binaries for macOS and Windows (64 bit) are also available. >> This is the eighth post-Christmas (production) release of Rakudo Star >> and implements Perl v6.c. It comes with support for the MoarVM backend >> (all module tests pass on supported platforms). >> IMPORTANT: "panda" is to be removed very shortly since it is >> deprecated. Please use "zef" instead. >> Currently, Star is on a quarterly release cycle and 2017.10 (October) >> will follow later this year. >> Please note that this release of Rakudo Star is not fully functional >> with the JVM backend from the Rakudo compiler. Please use the MoarVM >> backend only. >> In the Perl 6 world, we make a distinction between the language ("Perl >> 6") and specific implementations of the language such as "Rakudo >> Perl". >> This Star release includes release 2017.07 of the Rakudo Perl 6 >> compiler, version 2017.07 MoarVM, plus various modules, documentation, >> and other resources collected from the Perl 6 community. >> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather >> than the release NQP 2017.07 in order to fix the --ll-exception >> command line flag. >> The Rakudo compiler changes since the last Rakudo Star release of >> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md" >> under the "rakudo/docs/announce" directory of the source distribution. >> Notable changes in modules shipped with Rakudo Star: >> + DBIish: Doc and CI updates >> + doc: Too many to list. p6doc fixed. >> + grammar-debugger: Works again now. >> + p6-io-string: New dep for doc. >> + p6-native-resources: Removed since deprecated and not used by linenoise. >> + panda: Officially deprecate panda in favour of zef. >> + perl6-Test-When: New dep for perl6-pod-to-bigpage. >> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor. >> + tap-harness6: Replaces deprecated tap-harness6-prove6. >> + zef: Too many to list. >> There are some key features of Perl 6 that Rakudo Star does not yet >> handle appropriately, although they will appear in upcoming releases. >> Some of the not-quite-there features include: >> + advanced macros >> + non-blocking I/O (in progress) >> + some bits of Synopsis 9 and 11 >> There is an online resource at http://perl6.org/compilers/features >> that lists the known implemented and missing features of Rakudo's >> backends and other Perl 6 implementations. >> In many places we've tried to make Rakudo smart enough to inform the >> programmer that a given feature isn't implemented, but there are many >> that we've missed. Bug reports about missing and broken features are >> welcomed at rakudo...@perl.org. >> See https://perl6.org/ for links to much more information about Perl >> 6, including documentation, example code, tutorials, presentations, >> reference materials, design documents, and other supporting resources. >> Some Perl 6 tutorials are available under the "docs" directory in the >> release tarball. >> The development team thanks all of the contributors and sponsors for >> making Rakudo Star possible. If you would like to contribute, see >> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org >> mailing list, or join us on IRC #perl6 on freenode. > > > Any idea when the full Rakudo will be released? What do you mean by “the full Rakudo” ? Rakudo Star is the Rakudo compiler release with a set of useful modules added (“batteries included”). So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!