Re: [perl6/specs] 614b6f: doc with/without
with, without look awesome. -y On Sat, Aug 8, 2015 at 2:38 PM, GitHub nore...@github.com wrote: Branch: refs/heads/master Home: https://github.com/perl6/specs Commit: 614b6f36e1cae4c787e378bc6ab2afa1f86de1f0 https://github.com/perl6/specs/commit/614b6f36e1cae4c787e378bc6ab2afa1f86de1f0 Author: TimToady la...@wall.org Date: 2015-08-08 (Sat, 08 Aug 2015) Changed paths: M S04-control.pod Log Message: --- doc with/without
Re: [perl #125780] redefining $?FILE silently allowed
Fixed with 571b4fab525d4ebf7e0f63c , closable with tests
On 10 Aug 2015, at 14:48, Elizabeth Mattijsen (via RT)
perl6-bugs-follo...@perl.org wrote:
# New Ticket Created by Elizabeth Mattijsen
# Please include the string: [perl #125780]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/Ticket/Display.html?id=125780
[14:13:25] azawawi $?FILE is not working as expected
[14:13:48] azawawi $?FILE is still refering to
/home/azawawi/perl6-electron/.panda-work/1439208484_1/lib/Electron/App.pm6
[14:14:12] azawawi which panda create, installed and deleted that temp
directory
[14:14:18] azawawi s/create/created
[14:14:45] lizmat m: say $?FILE; { my $?FILE = foo; say $?FILE }
[14:14:47] +cameliarakudo-moar a32c14: OUTPUT«===SORRY!=== Error
while compiling /tmp/jsbZpo1BlkCannot use ? twigil on my variableat
/tmp/jsbZpo1Blk:1-- say $?FILE; { my $?FILE⏏ = foo; say $?FILE }»
[14:14:56] lizmat m: say $?FILE; { my constant $?FILE = foo; say $?FILE
}
[14:14:57] +cameliarakudo-moar a32c14:
OUTPUT«/tmp/bMlCVlwet8/tmp/bMlCVlwet8»
[14:15:04] lizmat hmmm
[14:18:32] azawawi lizmat: what's the point in having a compiled $?FILE
which panda totally ignores? :)
[14:19:11] azawawi my use case is that i need to find resources residing
in lib/Foo/resources directory
[14:19:55] lizmat there's %RESOURCE specced for that, alas NYI
[14:20:00] lizmat hmmm
[14:20:26] lizmat m: say $?FILE; { my constant $?FILE = foo; say $?FILE
} # actually feels like a bug
[14:20:29] +cameliarakudo-moar a32c14:
OUTPUT«/tmp/StJKSHy18K/tmp/StJKSHy18K»
[14:21:03] lizmat and I guess $?FILE should really be more runtime...
[14:21:14] azawawi $*FILE ?
[14:21:39] azawawi like http://perldoc.perl.org/functions/__FILE__.html
[14:22:42] lizmat yeah, but P5 doesn't have the concept of precomp, so
__FILE__ is always about the file that was just opened to be parsed
[14:33:07] jnthn I'd say the bug is that constant $?FILE = ... doesn't
complain the way my $?FILE = ... does.
[14:33:39] jnthn You shouldn't be able to declare $? things yourself,
they're special things for the compiler to resolve. And thus they're also
compile-time constants and frozen in pre-comp
[14:34:05] jnthn And no, $?FILE should not become more runtime.
[14:34:41] azawawi jnthn: what about when panda compiles them in a temp
folder .panda-work and then installs them? :)
[14:34:45] lizmat ok, I'll take that from there then
[14:36:09] jnthn azawawi: As I understand it, it probably should be
giving the files to a CompUnitRepo object to install, and leaving pre-comp to
Rakudo, in which case it can copy the file in place and pre-comp it in place.
[14:41:24] lizmat jnthn: eh, you should be able to define $?FOO yourself,
no? just not redefine existing ones?
[14:42:39] jnthn lizmat: I'm...not sure it makes a lot of sense to allow
that?
[14:43:45] lizmat ok, so no userland $?vars then
[14:44:03] lizmat I guess that'll make it easier to be sure to prevent
future collisions
[14:44:24] jnthn Right, it means we'll easily be able to introduce new
ones in the future knowing only the compiler gets to set them
[perl #125782] Uncaught exceptions in start { } blocks get no backtrace when raised via await
# New Ticket Created by Rob Hoelz # Please include the string: [perl #125782] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=125782 See the attached script. The original backtrace of an exception seems to vanish when awaiting a Promise throws that exception.
[perl #125783] callsame does not work more than once (callsame; callsame; callsame;)
# New Ticket Created by Alex Jakimenko
# Please include the string: [perl #125783]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/Ticket/Display.html?id=125783
Code:
sub foo { say 'X' };
foo.wrap:{ callsame; callsame; callsame };
foo;
Result:
X
I expected this:
X
X
X
Another interesting code snippet:
sub foo { say 'X' };
foo.wrap:{ callsame; callsame; nextsame; say 'y' };
foo;
Which, surprisingly, prints this:
X
y
IRC log: http://irclog.perlgeek.de/perl6/2015-08-10#i_11036336 and
http://irclog.perlgeek.de/perl6/2015-08-11#i_11036346
[perl #125784] Negative overflow in Str.index $startpos
# New Ticket Created by Alex Jakimenko # Please include the string: [perl #125784] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/Ticket/Display.html?id=125784 Code: say index 'xxy', 'y', -999; say index 'xxy', 'y', -; Result: Nil 2
[perl #125771] Rakudo on OS X 10.6.8
On Sun Aug 09 20:09:50 2015, coke wrote: On Sun Aug 09 20:04:17 2015, coke wrote: If we're using autodie in the perl5 Configure script, that's an implicit dependency on 5.10.1 ; the declared dep is on 5.10.0, however. I'll update the scripts to make it explicit, but in the meantime, please try the build with a newer version of Perl 5. Regards. Looks like MoarVM was the only place this happened. The next Star release should include this bugfix - in the meantime, if you use a recent version of perl5, you should be fine. Shortly after I did this, someone submitted a patch that removes the requirement for 5.10.1 and made it 5.10.0 compatible. If you apply https://github.com/MoarVM/MoarVM/commit/e075ba6993c6296999bceca4a9415dc5e5f58a17 to the copy of MoarVM shipped with Rakudo Star (ignoring the line that puts the version back to the original version, since you don't have that change), then you should be able to build with 5.10.0 Regards. -- Will Coke Coleda
[perl #125780] redefining $?FILE silently allowed
# New Ticket Created by Elizabeth Mattijsen
# Please include the string: [perl #125780]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/Ticket/Display.html?id=125780
[14:13:25] azawawi $?FILE is not working as expected
[14:13:48] azawawi $?FILE is still refering to
/home/azawawi/perl6-electron/.panda-work/1439208484_1/lib/Electron/App.pm6
[14:14:12] azawawi which panda create, installed and deleted that temp
directory
[14:14:18] azawawi s/create/created
[14:14:45] lizmatm: say $?FILE; { my $?FILE = foo; say $?FILE }
[14:14:47] +camelia rakudo-moar a32c14: OUTPUT«===SORRY!=== Error while
compiling /tmp/jsbZpo1BlkCannot use ? twigil on my variableat
/tmp/jsbZpo1Blk:1-- say $?FILE; { my $?FILE⏏ = foo; say $?FILE }»
[14:14:56] lizmatm: say $?FILE; { my constant $?FILE = foo; say $?FILE
}
[14:14:57] +camelia rakudo-moar a32c14:
OUTPUT«/tmp/bMlCVlwet8/tmp/bMlCVlwet8»
[14:15:04] lizmathmmm
[14:18:32] azawawi lizmat: what's the point in having a compiled $?FILE
which panda totally ignores? :)
[14:19:11] azawawi my use case is that i need to find resources residing
in lib/Foo/resources directory
[14:19:55] lizmatthere's %RESOURCE specced for that, alas NYI
[14:20:00] lizmathmmm
[14:20:26] lizmatm: say $?FILE; { my constant $?FILE = foo; say $?FILE
} # actually feels like a bug
[14:20:29] +camelia rakudo-moar a32c14:
OUTPUT«/tmp/StJKSHy18K/tmp/StJKSHy18K»
[14:21:03] lizmatand I guess $?FILE should really be more runtime...
[14:21:14] azawawi $*FILE ?
[14:21:39] azawawi like http://perldoc.perl.org/functions/__FILE__.html
[14:22:42] lizmatyeah, but P5 doesn't have the concept of precomp, so
__FILE__ is always about the file that was just opened to be parsed
[14:33:07] jnthn I'd say the bug is that constant $?FILE = ... doesn't
complain the way my $?FILE = ... does.
[14:33:39] jnthn You shouldn't be able to declare $? things yourself,
they're special things for the compiler to resolve. And thus they're also
compile-time constants and frozen in pre-comp
[14:34:05] jnthn And no, $?FILE should not become more runtime.
[14:34:41] azawawi jnthn: what about when panda compiles them in a temp
folder .panda-work and then installs them? :)
[14:34:45] lizmatok, I'll take that from there then
[14:36:09] jnthn azawawi: As I understand it, it probably should be
giving the files to a CompUnitRepo object to install, and leaving pre-comp to
Rakudo, in which case it can copy the file in place and pre-comp it in place.
[14:41:24] lizmatjnthn: eh, you should be able to define $?FOO yourself,
no? just not redefine existing ones?
[14:42:39] jnthn lizmat: I'm...not sure it makes a lot of sense to allow
that?
[14:43:45] lizmatok, so no userland $?vars then
[14:44:03] lizmatI guess that'll make it easier to be sure to prevent
future collisions
[14:44:24] jnthn Right, it means we'll easily be able to introduce new
ones in the future knowing only the compiler gets to set them
