# New Ticket Created by "Brian S. Julin"
# Please include the string: [perl #127018]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127018 >
(12:04:56 AM) cxreg: skids: i discovered this trying to go through the exercism
per
Alex Jakimenko via RT wrote:
>See this: https://rt.perl.org/Public/Bug/Display.html?id=126990
Ah, quite right. My [perl #127011] duplicates the "LTA error message"
portion of your [perl #126990]. Mine can therefore be closed, if the
.Range portion of yours doesn't confound dealing with the issue
On Wed, Dec 23, 2015 at 9:40 PM, Zefram
wrote:
> Is it legal to compile code that, if executed, would always produce
> an exception? Rakudo seems conflicted on the matter.
>
Pretty sure better compile time checking is a known issue and was not
expected or intended to be resolved by the first re
# New Ticket Created by Zefram
# Please include the string: [perl #127017]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127017 >
> (1 but 7).fmt("%02d")
P6opaque: get_boxed_ref could not unbox for the representation '20'
Pr
# New Ticket Created by Zefram
# Please include the string: [perl #127016]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127016 >
Date.new permits the construction of a Date object with the undefined
Int type object as the ye
# New Ticket Created by Zefram
# Please include the string: [perl #127015]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127015 >
> Date.new(:year).year
True
It is less than awesome that the .year method on a Date object ret
# New Ticket Created by Zefram
# Please include the string: [perl #127014]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127014 >
Is it legal to compile code that, if executed, would always produce
an exception? Rakudo seems
# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #127012]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127012 >
Code:
gather for ^3 -> $a, $b { take 1 }
Result:
===SORRY!===
Too few positionals pass
# New Ticket Created by Zefram
# Please include the string: [perl #127011]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127011 >
> my Int $a = Inf
Cannot find method 'value'
> my Int $a = NaN
Cannot find method 'value'
It i
Commit 895546990f6001a5999ef, attempting to fix [perl #127004], has
added some more kinds of non ISO 8601 string that are accepted as input.
-zefram
Elizabeth Mattijsen via RT wrote:
>Fixed with 895546990f6001a5999ef
With that edit, some invalid year representations are now accepted on
input, such as "-" and "12345". They add to the scope of [perl
#127002].
-zefram
# New Ticket Created by Zefram
# Please include the string: [perl #127010]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127010 >
Date.new on a Str input only accepts non-negative year numbers:
> Date.new("-1234-01-01")
Inva
> On 24 Dec 2015, at 00:08, Zefram (via RT)
> wrote:
>
> # New Ticket Created by Zefram
> # Please include the string: [perl #127007]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=127007 >
>
>
> DateTime.Str is documen
> On 23 Dec 2015, at 23:16, Zefram (via RT)
> wrote:
>
> # New Ticket Created by Zefram
> # Please include the string: [perl #127004]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=127004 >
>
>
> DateTime.new on a Str i
# New Ticket Created by Zefram
# Please include the string: [perl #127008]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127008 >
The documentation for Date.new says that when given a string input the
string is to be in ISO 8
Elizabeth Mattijsen via RT wrote:
>I tend to say ENOTABUG, as they are cases of "be liberal in what you
>accept" and they match the regular expression.
If the code is not a bug, then the documentation is, because it explicitly
says that invalid input will result in an exception. You're welcome to
# New Ticket Created by Zefram
# Please include the string: [perl #127007]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127007 >
DateTime.Str is documented to produce output in ISO 8601 format by
default, but the formatting
> On 23 Dec 2015, at 23:11, Zefram (via RT)
> wrote:
>
> # New Ticket Created by Zefram
> # Please include the string: [perl #127003]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=127003 >
>
>
> DateTime.new on a Str
# New Ticket Created by Zefram
# Please include the string: [perl #127006]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127006 >
> my $a = DateTime.new(:year(2000), :hour(13), :timezone(3600)); $a.Str
2000-01-01T13:00:00+01:
# New Ticket Created by Zefram
# Please include the string: [perl #127005]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127005 >
Internally DateTime allows its seconds value to be any kind of numeric
value in the right range
> On 23 Dec 2015, at 23:07, Zefram (via RT)
> wrote:
>
> # New Ticket Created by Zefram
> # Please include the string: [perl #127002]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=127002 >
>
>
> The documentation for
# New Ticket Created by Zefram
# Please include the string: [perl #127004]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127004 >
DateTime.new on a Str input only accepts years in the range 0 to
inclusive. The class is
# New Ticket Created by Zefram
# Please include the string: [perl #127003]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127003 >
DateTime.new on a Str input, per ISO 8601:2004 clause 4.2.2.4, attempts to
accept either comma
# New Ticket Created by Zefram
# Please include the string: [perl #127002]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127002 >
The documentation for DateTime.new says that when given a string input
the string is to be in I
# New Ticket Created by A. Sinan Unur
# Please include the string: [perl #126993]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126993 >
When running the test with the original file which has:
is_run $x, :args['-e', "print q
# New Ticket Created by Matt Oates
# Please include the string: [perl #126997]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126997 >
If no other numeric literal is given as a base along with the unicode
exponent characters e
# New Ticket Created by Alexander Hartmaier
# Please include the string: [perl #127001]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=127001 >
I wasn't able to come up with a failing test case as scripts aren't precompiled
a
On Wed, Dec 23, 2015 at 11:43 AM, Elizabeth Mattijsen wrote:
>> On 23 Dec 2015, at 18:32, Tom Browder wrote:
...
>> BTW, will that RAM be required always for Perl 6, or just during the
>> installation?
>
> Just during compilation really.
Thanks, Liz, that's good news.
Reporting success after in
> On 23 Dec 2015, at 18:32, Tom Browder wrote:
>
> On Wed, Dec 23, 2015 at 10:38 AM, Steve Mynott wrote:
>> That looks like you don't have enough virtual memory (the physical
>> memory assigned to your VM and swap within it) should be at least 2GB
>> (maybe even more).
>
> Thanks, Steve--I wasn
On Wed, Dec 23, 2015 at 10:38 AM, Steve Mynott wrote:
> That looks like you don't have enough virtual memory (the physical
> memory assigned to your VM and swap within it) should be at least 2GB
> (maybe even more).
Thanks, Steve--I wasn't very bright, was I!
I have increased the VM guest's RAM
On Tue Dec 22 05:30:41 2015, alex.jakime...@gmail.com wrote:
> Code:
> enum Animal (Cat, Dog)
>
> Result:
> ===SORRY!===
> Cannot invoke this object
>
>
> Well, the error message is not so good, but you can say “who is going to do
> that anyway?”. Well, consider this:
>
> Code:
> enum Animal (C
That looks like you don't have enough virtual memory (the physical
memory assigned to your VM and swap within it) should be at least 2GB
(maybe even more).
S
On 23 December 2015 at 16:27, Tom Browder wrote:
> I'm getting a "rakudobrew build moar" failure on Ubuntu 14.04 LTS,
> 32-bit, running as
I'm getting a "rakudobrew build moar" failure on Ubuntu 14.04 LTS,
32-bit, running as a guest host on VirtualBox 5.0.12 r104815 (running
on Debian 7, 64-bit).
Note that I have done some root cpanm Perl module installations as
well as some Ubuntu package manager installations of Perl modules,
mostl
# New Ticket Created by Vytautas D
# Please include the string: [perl #126998]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=126998 >
Following script throws error ( "Aborted (core dumped)" ) when $id ==
1007. This is because
Fixed in 02588190492349fabde00c5a15b873ea61a9333e
Tested in 2f126a3ab7d0991767ca84c562b8f3ae97b25c4e
There are no tests there for with or whenever, but those did not appear to
misbehave when I tried them on the command line. Feel free to add more tests
for those.
35 matches
Mail list logo
