This was fixed by Zoffix one month ago (including tests):
https://rt.perl.org/Ticket/Display.html?id=131222#txn-1458062
Closing.
Nice.
I think this would be a good addition to the docs :)
You can also write
$*PROGRAM.parent.parent.parent.parent.absolute;
but if your relative path is too short, you might end up with a bunch
of .. like this:
/Users/gabor/work/perl6maven.com/../..
Gabor
On Sun, May 28, 2017 at 9:10 AM
After thinking about what Zoffix said, probably what you're meant to do is:
$*PROGRAM.parent.absolute
Which leaves the stringification (.absolute) until last.
On Sun, May 28, 2017 at 4:04 PM Lloyd Fournier
wrote:
> FYI:
>
> 15:57 < llfourn> Zoffix: is there any plan to make .dirname and .absol
FYI:
15:57 < llfourn> Zoffix: is there any plan to make .dirname and .absolute
on IO::Path return an IO::Path?
15:58 < llfourn> (rather than a Str)
15:58 < Zoffix> llfourn: no
15:58 < Zoffix> .absolute is one of the two ways to stringify an IO::Path
(the second being .relative)
15:58 < Zoffix> And
thanks.
$*PROGRAM.dirname.IO.absolute;
also works, but yours seem better.
As a side note, dirname does not return and IO::Path object either.
Gabor
On Sat, May 27, 2017 at 6:48 PM, Lloyd Fournier wrote:
> I'd use
>
> $*PROGRAM.absolute.IO.dirname
>
> I'm not sure why .absolute doesn't return
A bit late, but thanks to both of you :)
Gabor
On Tue, May 2, 2017 at 6:33 PM, Gianni Ceccarelli
wrote:
> On Tue, 2 May 2017 17:02:40 +0200
> Gabor Szabo wrote:
>> Is there some way in Perl 6 to tell if a file was executed directly or
>> loaded into memory as a module?
>
> One way that seems to
Excellent. Thanks.
Gabor
On Fri, May 26, 2017 at 1:15 PM, Elizabeth Mattijsen wrote:
> Fixed with https://github.com/rakudo/rakudo/commit/f2fca0c8c2 .
>
>> On 26 May 2017, at 10:47, Brent Laabs wrote:
>>
>> To file a bug in Rakudo, you should email rakudo...@perl.org.
>>
>> If it's a better err
I bisected MoarVM and the offending commit is here:
https://github.com/MoarVM/MoarVM/commit/c98634cf2542874d7daa5b45f77f7de4cf04a081
From what I see, this commit did not actually cause the root bug, it just
exposed it.
The Unicode Database was rebuilt so that NFG_QC=False for Emoji characters,
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131387]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131387 >
$z is `Nil` without my having to assign anything, while `$!z` is Any. To make
`$!z` Nil I
# New Ticket Created by hanenkamp
# Please include the string: [perl #131386]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131386 >
See http://colabti.org/irclogger/irclogger_log/perl6?date=2017-05-27#l799
[23:24] m: my %x
# New Ticket Created by Dan Miller
# Please include the string: [perl #131381]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131381 >
This is Rakudo version 2017.04.3 built on MoarVM version 2017.04-53-g66c6dda
implementing
# New Ticket Created by Daniel Green
# Please include the string: [perl #131385]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131385 >
So `nqp-m -e 'say(19)'` prints `100016`.
See https://irclog.
> On 27 May 2017, at 23:22, Elizabeth Mattijsen wrote:
>> On 27 May 2017, at 19:33, Marcel Timmerman wrote:
>> In perl6 version 2017.04.3-287-g3e7675a built on MoarVM version
>> 2017.04-64-g6d5ea04
>> implementing Perl 6.c. I observe the following;
>>
>> my Num $num = Inf;
>> my FatRat $f = $nu
> On 27 May 2017, at 19:33, Marcel Timmerman wrote:
> In perl6 version 2017.04.3-287-g3e7675a built on MoarVM version
> 2017.04-64-g6d5ea04
> implementing Perl 6.c. I observe the following;
>
> my Num $num = Inf;
> my FatRat $f = $num.FatRat;
> Type check failed in assignment to $f; expected F
Hi,
In perl6 version 2017.04.3-287-g3e7675a built on MoarVM version
2017.04-64-g6d5ea04
implementing Perl 6.c. I observe the following;
my Num $num = Inf;
my FatRat $f = $num.FatRat;
Type check failed in assignment to $f; expected FatRat but got
Rational[Num,Int] (?)
in block at line 1
I'd use
$*PROGRAM.absolute.IO.dirname
I'm not sure why .absolute doesn't return an IO::Path object. Maybe that's
being addressed as part of Zoffix++'s IO work.
On Sat, May 27, 2017 at 10:07 PM Gabor Szabo wrote:
> I came up with this:
>
> say $*PROGRAM-NAME.IO.absolute.IO.dirname;
>
> but I wo
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131384]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131384 >
c: HEAD with "/tmp/foo2121".IO { .spurt: "fo♥o"; with
.open(:enc) { say .slurp } }
Zoff
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131383]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131383 >
Seems something with decoding actually, since using char of different size or
adding anot
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev
# Please include the string: [perl #131382]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131382 >
Code:
for(^700){say 2}
Result:
===SORRY!=== Error while compiling -e
On Fri, 26 May 2017 23:10:58 -0700, n...@detonation.org wrote:
> Can you please re-run with RAKUDO_MODULE_DEBUG=1?
See attached.
> I bet, there's a file handle left open somewhere.
Indeed, I fixed this by closing an open filehandle; please check the close is
in a right place:
https://github.com
On Fri, 26 May 2017 23:10:58 -0700, n...@detonation.org wrote:
> Can you please re-run with RAKUDO_MODULE_DEBUG=1?
See attached.
> I bet, there's a file handle left open somewhere.
Indeed, I fixed this by closing an open filehandle; please check the close is
in a right place:
https://github.com
I came up with this:
say $*PROGRAM-NAME.IO.absolute.IO.dirname;
but I wonder if there is a simpler way to do it?
regards
Gabor
FWIW, I can’t get this to break on 2017.05. Please note that a *LOT* of
concurrency fixes landed after 2016.04. I suggest you use a more current
version, preferably 2017.05. Unless this problem can be confirmed on a more
recent Rakudo version, I suggest this ticket can be closed.
> On 25 May
FWIW, I can’t get this to break on 2017.05. Please note that a *LOT* of
concurrency fixes landed after 2016.04. I suggest you use a more current
version, preferably 2017.05. Unless this problem can be confirmed on a more
recent Rakudo version, I suggest this ticket can be closed.
> On 25 May
24 matches
Mail list logo
