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
Zoffix Znet via RT skribis 2017-07-24 10:51 (-0700):
> But the error for that code does already say `in sub bar`:
> m: sub bar {}; bar :42foo
> rakudo-moar 2fb8c7: OUTPUT: «Unexpected named argument 'foo' passed in
> sub bar at line 1
I was catching exceptions and printing them
Zoffix Znet via RT skribis 2017-07-24 10:51 (-0700):
> But the error for that code does already say `in sub bar`:
> m: sub bar {}; bar :42foo
> rakudo-moar 2fb8c7: OUTPUT: «Unexpected named argument 'foo' passed in
> sub bar at line 1
I was catching exceptions and printing them
Some additional testing. If I disable IPv6 on my ethernet adapter,
everything works. If I re-enable IPv6, it no longer works. Possibly
something on my end? but all other software and dev environments work
normally without disabling IPv6.
Mike Lowe
(513) 417-0570
mlowe31...@gmail.com
On Sat, Jul
Some additional testing. If I disable IPv6 on my ethernet adapter,
everything works. If I re-enable IPv6, it no longer works. Possibly
something on my end? but all other software and dev environments work
normally without disabling IPv6.
The OP said :?foo should work because :foo and :!foo work. I don't follow
the logic. How are those things related? Why should :foo and :!foo imply
:?foo? (In my head it makes as much sense as ":foo and :!foo implies
:*foo", which is to say, none.)
I don't see any benefit to adding a :?foo
# New Ticket Created by Michael Lowe
# Please include the string: [perl #131778]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131778 >
Hello,
I've run into a bug in IO::Socket::INET.
Windows 10
perl6 -v
This is Rakudo
I've just uploaded the Win64 version and I'm still building the Mac
one (which won't take long)
S
On 24 July 2017 at 20:29, wrote:
>
> Quoting Darren Duncan :
>
>> On 2017-07-24 11:40 AM, Steve Mynott wrote:
>>>
>>> A useful and usable production
Quoting Darren Duncan :
On 2017-07-24 11:40 AM, Steve Mynott wrote:
A useful and usable production distribution of Perl 6
The download links on http://rakudo.org/how-to-get-rakudo/ still
name the April release and will need updating. -- Darren Duncan
I updated
On 2017-07-24 11:40 AM, Steve Mynott wrote:
A useful and usable production distribution of Perl 6
The download links on http://rakudo.org/how-to-get-rakudo/ still name the April
release and will need updating. -- Darren Duncan
> On 24 Jul 2017, at 19:51, Zoffix Znet via RT
> wrote:
>
> On Mon, 24 Jul 2017 07:15:54 -0700, ju...@tnx.nl wrote:
>> It would be more awesome if "Unexected named argument 'foo' passed" was
>> supplemented with the name of the function to which it was passed.
>>
> On 24 Jul 2017, at 19:51, Zoffix Znet via RT
> wrote:
>
> On Mon, 24 Jul 2017 07:15:54 -0700, ju...@tnx.nl wrote:
>> It would be more awesome if "Unexected named argument 'foo' passed" was
>> supplemented with the name of the function to which it was passed.
>>
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
On Mon, 24 Jul 2017 07:15:54 -0700, ju...@tnx.nl wrote:
> It would be more awesome if "Unexected named argument 'foo' passed" was
> supplemented with the name of the function to which it was passed.
>
> sub xyzzy ($x, :$foo = False) { ... }
> sub bar ($y) { ... }
>
> xyzzy(
>
On Mon, 24 Jul 2017 07:15:54 -0700, ju...@tnx.nl wrote:
> It would be more awesome if "Unexected named argument 'foo' passed" was
> supplemented with the name of the function to which it was passed.
>
> sub xyzzy ($x, :$foo = False) { ... }
> sub bar ($y) { ... }
>
> xyzzy(
>
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131791]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131791 >
The coercion works fine here:
17:03 Zoffix m: class B {…}; class A { method B { B.new
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131790]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131790 >
m: my @a is default(42) = 1...*; @a[1]:delete; say @a[1]:exists; .say for
@a[^10]
# New Ticket Created by Juerd Waalboer
# Please include the string: [perl #131789]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131789 >
It would be more awesome if "Unexected named argument 'foo' passed" was
supplemented
On Sat, 22 Jul 2017 09:12:31 -0700, c...@zoffix.com wrote:
> On Sat, 22 Jul 2017 07:53:26 -0700, alex.jakime...@gmail.com wrote:
> > This should work:
> >
> > Code:
> > say (:?foo);
> >
> > Result:
> > ===SORRY!=== Error while compiling -e
> > Bogus statement
> > at -e:1
> > --> say (:⏏?foo);
On Sat, 22 Jul 2017 09:12:31 -0700, c...@zoffix.com wrote:
> On Sat, 22 Jul 2017 07:53:26 -0700, alex.jakime...@gmail.com wrote:
> > This should work:
> >
> > Code:
> > say (:?foo);
> >
> > Result:
> > ===SORRY!=== Error while compiling -e
> > Bogus statement
> > at -e:1
> > --> say (:⏏?foo);
> On 23 Jul 2017, at 22:27, Sam S. via RT wrote:
>
>> Which then goes back to: what is the use case of Slipping an Array?
>
> Same as slipping any other type of Iterable: Fine-grained, elegant flattening
> and concatenating.
>
> Compare:
>
> my @all = flat
> On 23 Jul 2017, at 22:27, Sam S. via RT wrote:
>
>> Which then goes back to: what is the use case of Slipping an Array?
>
> Same as slipping any other type of Iterable: Fine-grained, elegant flattening
> and concatenating.
>
> Compare:
>
> my @all = flat
22 matches
Mail list logo