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/
A
On 21 July 2017 at 09:07, Mark Carter wrote:
> 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 Raku
On Tue, Jul 25, 2017 at 5:41 PM, Darren Duncan
wrote:
> 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
>> p
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 Rak
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 Allbery wrote:
> On Tue, Jul 25, 2017 at 3:37 PM, Mark Car
".gist" is probably the wrong answer in this case.
my @got = ‘one’, ‘two three’; say @got # OUTPUT: [one two three]
↑ Not very useful
On 2017-07-25 12:52:25, alex.jakime...@gmail.com wrote:
> Sometimes it is useful to test the input against regexes. Let's try:
>
> Code:
> use Test;
> cmp-ok ‘foo
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131797]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131797 >
Sometimes it is useful to test the input against regexes. Let's try:
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
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.
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
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
Perl6 Developers,
Thank you for your efforts. I'm having a great time working with this
language. As a systems person, I'm getting the feeling that this might
actually be the "last language I ever have to learn" (cite: Wall). My
cantankerous `command` outputs are now very manageable. Concur
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 wh
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 instal
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 highlight
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' defin
On 2017-07-25 8:32 AM, Steve Mynott wrote:
On 25 July 2017 at 16:23, Darren Duncan wrote:
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 langua
On 25 July 2017 at 16:33, Stephen Wilcoxon wrote:
> 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
"P
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
On 25 July 2017 at 16:23, Darren Duncan wrote:
> 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
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
Based on the tally of the opinions, I'm rejecting this ticket:
AlexDaniel: +1
Zoffix: -1
Jonathan Scott Duff: -1
Coke: -1
> Sorry for being think but what is say (:?foo); meant to do? The OP just says
> it should "work".
I think that's pretty good evidence the extra syntax does
Based on the tally of the opinions, I'm rejecting this ticket:
AlexDaniel: +1
Zoffix: -1
Jonathan Scott Duff: -1
Coke: -1
> Sorry for being think but what is say (:?foo); meant to do? The OP just says
> it should "work".
I think that's pretty good evidence the extra syntax does
merged patch: https://github.com/rakudo/rakudo/pull/
tests: https://github.com/perl6/roast/pull/291/files
can be closed
On Fri, Apr 8, 2016 at 7:16 PM grond...@yahoo.fr <
perl6-bugs-follo...@perl.org> wrote:
> # New Ticket Created by grond...@yahoo.fr
> # Please include the string: [perl #1
merged patch: https://github.com/rakudo/rakudo/pull/
tests: https://github.com/perl6/roast/pull/291/files
can be closed
On Fri, Apr 8, 2016 at 7:16 PM grond...@yahoo.fr <
perl6-bugs-follo...@perl.org> wrote:
> # New Ticket Created by grond...@yahoo.fr
> # Please include the string: [perl #1
merged patch: https://github.com/rakudo/rakudo/pull/
tests: https://github.com/perl6/roast/pull/291/files
can be closed
On Wed, Jul 5, 2017 at 3:42 PM Lloyd Fournier
wrote:
> # New Ticket Created by Lloyd Fournier
> # Please include the string: [perl #131705]
> # in the subject line of all
merged patch: https://github.com/rakudo/rakudo/pull/
tests: https://github.com/perl6/roast/pull/291/files
can be closed
On Wed, Jul 5, 2017 at 3:42 PM Lloyd Fournier
wrote:
> # New Ticket Created by Lloyd Fournier
> # Please include the string: [perl #131705]
> # in the subject line of all
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.
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
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.
>
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, ToddA
> 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
>>
32 matches
Mail list logo