[perl #124006] [BUG] Callable roles fail to compile with non-meta method calls on self

2017-09-26 Thread Brian S. Julin via RT
On Fri, 06 Mar 2015 14:10:06 -0800, rayd...@cyberuniverses.com wrote: > See http://irclog.perlgeek.de/perl6/2015-03-06#i_10237431 and the next > few examples. > > perl6 -e 'role R does Callable { method foo { self.say } }' > ===SORRY!=== > Internal error: failed to remove block > > Removing the C

Re: user and group of a file?

2017-09-26 Thread Brandon Allbery
On Tue, Sep 26, 2017 at 11:02 AM, Parrot Raiser <1parr...@gmail.com> wrote: > This is the capability provided by Perl 5's "stat". Would a clone with > the same properties and behaviours be the right thing, or are there > "features" to fix? Same features, probably. It is just one of those things

[perl #132170] fork + react + IO::Socket::Async issue

2017-09-26 Thread via RT
# New Ticket Created by Brian Duggan # Please include the string: [perl #132170] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132170 > When I export a function that does a fork() and then a react + whenever + IO::Socket::Asy

[perl #132169] Using ::Foo type capture as default causes inconsistent bind result

2017-09-26 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #132169] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132169 > IRC: https://irclog.perlgeek.de/perl6/2017-09-26#i_15219996 I kinda expected the first ve

Re: [perl #131626] [PERF] ≥ and ≤ are 36x slower than Texas version; ≠ is 15x slower

2017-09-26 Thread Parrot Raiser
Obviously, that fixes the immediate problem, but is there any clue as to the reason for the extraordinary difference in performance? Where's it happening? I can see it taking longer for the parser to look up the characters, but shouldn't the original translation have reduced that to a common form

[perl #131626] [PERF] ≥ and ≤ are 36x slower than Texas version; ≠ is 15x slower

2017-09-26 Thread Zoffix Znet via RT
On Thu, 22 Jun 2017 10:29:59 -0700, c...@zoffix.com wrote: > I'd expect the fancy Unicode versions of <=, >=, and != to perform > equally well, instead the > ≥ and ≤ are 36x slower than their Texas companions and ≠ is 15x > slower. > > Here's the timings for >= vs ≥: > > m: my $x = rand; for ^100

[perl #131626] [PERF] ≥ and ≤ are 36x slower than Texas version; ≠ is 15x slower

2017-09-26 Thread Zoffix Znet via RT
On Thu, 22 Jun 2017 10:29:59 -0700, c...@zoffix.com wrote: > I'd expect the fancy Unicode versions of <=, >=, and != to perform > equally well, instead the > ≥ and ≤ are 36x slower than their Texas companions and ≠ is 15x > slower. > > Here's the timings for >= vs ≥: > > m: my $x = rand; for ^100

[perl #132168] [LTA] Mention context when suspecting runaway quotes (say "foo'; my $x = 42;)

2017-09-26 Thread via RT
# New Ticket Created by Aleks-Daniel Jakimenko-Aleksejev # Please include the string: [perl #132168] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132168 > Code: say "foo'; my $x = 42; Result: ===SORRY!=== Error while compi

Re: user and group of a file?

2017-09-26 Thread Parrot Raiser
This is the capability provided by Perl 5's "stat". Would a clone with the same properties and behaviours be the right thing, or are there "features" to fix? On 9/26/17, Brandon Allbery wrote: > On Tue, Sep 26, 2017 at 2:11 AM, ToddAndMargo > wrote: > >> Does Perl 6 have one of those fancy subs

Re: user and group of a file?

2017-09-26 Thread Brandon Allbery
On Tue, Sep 26, 2017 at 2:11 AM, ToddAndMargo wrote: > Does Perl 6 have one of those fancy subs that will tell me > the user and group association of a file? Or do I just > make a system call to "ls"? > At the moment you'll have to use ls. There's an ecosystem want out for a POSIX support modul

Re: Need a second pair of eyes

2017-09-26 Thread Brandon Allbery
This explanation confuses me a bit, actually. (more inline) On Tue, Sep 26, 2017 at 9:45 AM, Larry Wall wrote: > In slightly greater detail, we're currently treating an undeclared > variable as a syntax error rather than a semantic error, and we treat > those differently. Syntax errors are usua

Re: Need a second pair of eyes

2017-09-26 Thread Larry Wall
On Mon, Sep 25, 2017 at 10:25:42AM -0400, Brandon Allbery wrote: : So as to make this not entirely content-free: I would suggest that the : string language note the line on which it sees a bare newline, and if it : subsequently hits a syntax error while still parsing that string it could : output s

undeclared variables inside double-quoted string lwas: Re: Need a second pair of eyes]

2017-09-26 Thread Timo Paulssen
On 26/09/17 04:26, Brandon Allbery wrote: > On Mon, Sep 25, 2017 at 10:23 PM, ToddAndMargo > wrote: > > On 09/25/2017 07:25 AM, Brandon Allbery wrote: > > So as to make this not entirely content-free: I would suggest > that the string language note

[perl #132166] [REGEX] Excluded endpoints with Ranges in regex quantifiers don't get excluded

2017-09-26 Thread Zoffix Znet via RT
On Tue, 26 Sep 2017 03:15:03 -0700, c...@zoffix.com wrote: > Expected the first to not match and second to match at most 2 "x"es > > m: say "x" ~~ / "x" ** {1^..3}/ > rakudo-moar 8cf083: OUTPUT: «｢x｣␤» > m: say "xx" ~~ / "x" ** {1^..^3}/ > rakudo-moar 8cf083: OUTPUT: «｢xxx｣␤» Dupe of RT#1

[perl #132166] [REGEX] Excluded endpoints with Ranges in regex quantifiers don't get excluded

2017-09-26 Thread via RT
# New Ticket Created by Zoffix Znet # Please include the string: [perl #132166] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=132166 > Expected the first to not match and second to match at most 2 "x"es m: say "x" ~~ / "x"