On Wed, 28 Dec 2016 19:46:01 -0800, alex.jakime...@gmail.com wrote:
> Code:
> unit module Foo; sub foo() is export {}; say Foo::EXPORT ===
> UNIT::EXPORT # unit makes the declared package the current UNIT
>
> Result (2016.04):
> True
>
> Result (HEAD):
> False
>
>
> Bisectable is pointing to
>
# New Ticket Created by Christopher Bottoms
# Please include the string: [perl #131927]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131927 >
When heredoc bodies are preceded by spaces, but the body itself contains a tab,
s
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131925]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131925 >
Code:
say so $*DISTRO.Str|$*KERNEL.Str ~~ /linux/
Result:
True
Cod
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131924]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131924 >
The issue happens in Email::Simple (one of its tests is now failing,
Several areas of the docs then need to correct that. No matter what you
decide, a user should be able to take the tricky words in an error message
and usefully find them in the docs.
--
brian d foy
http://www.pair.com/~comdog/
Several areas of the docs then need to correct that. No matter what you
decide, a user should be able to take the tricky words in an error message
and usefully find them in the docs.
--
brian d foy
http://www.pair.com/~comdog/
Only *@foo and *%foo are slurpy, as in "slurping up the rest of the arguments.
But the term "variadic" refers to all optional arguments including named ones,
so it would be incorrect to call those "slurpy", because they don't. It's like
the difference between * and ? in regex.
Larry
On Fri, 1
Only *@foo and *%foo are slurpy, as in "slurping up the rest of the arguments.
But the term "variadic" refers to all optional arguments including named ones,
so it would be incorrect to call those "slurpy", because they don't. It's like
the difference between * and ? in regex.
Larry
On Fri, 1
Another way to do it is to support custom nl (similarly to how we do
｢$*IN.nl-in = 0.chr｣ now). Split may be an overkill.
On 2017-08-18 08:40:32, c...@zoffix.com wrote:
> On Fri, 18 Aug 2017 08:35:18 -0700, alex.jakime...@gmail.com wrote:
> > Most command line tools support zero-separated input an
This could've been a LHF, except for these tests:
https://github.com/perl6/roast/blob/4bfd6d2374cb4ea1b8fa057a5f294b988e4dec44/S32-exceptions/misc.t#L180-L185
¯\_(ツ)_/¯
But yes, I think it should say “slurpy” everywhere.
On 2017-08-18 07:10:52, comdog wrote:
> Consider this program which I don't
On Fri, 18 Aug 2017 08:35:18 -0700, alex.jakime...@gmail.com wrote:
> Most command line tools support zero-separated input and output (grep
> -z, find -print0, perl -0, sort -z, xargs -0, sed -z).
>
> And while you can use .stdout.lines to work on things line-by-line,
> doing the same thing with n
On Fri, 18 Aug 2017 08:35:18 -0700, alex.jakime...@gmail.com wrote:
> Most command line tools support zero-separated input and output (grep
> -z, find -print0, perl -0, sort -z, xargs -0, sed -z).
>
> And while you can use .stdout.lines to work on things line-by-line,
> doing the same thing with n
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131923]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131923 >
Most command line tools support zero-separated input and output (grep
# New Ticket Created by "brian d foy"
# Please include the string: [perl #131922]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131922 >
Consider this program which I don't expect to work (and it doesn't compile):
sub sh
14 matches
Mail list logo
