[perl #126732] [RFC] Problem with superscripts when there is no number in front of it (³² == 9)

FWIW, I rescind all of my previous comments on the matter and now think no special casing should be done to error out on ³² or anything like that. The only people I see complaining about it are those who just type it up randomly to see what it'd do; i.e. not an issue in real programs. I see no

[perl #131505] [@LARRY] Special case allomorph coercion everywhere

On Sat, 03 Jun 2017 21:20:49 -0700, c...@zoffix.com wrote: > (found in discussion in > https://rt.perl.org/Ticket/Display.html?id=131493 ) > > > We have some special casing for coercion of allomorphs in some > instances, which > is done so there'd be some way to force one of the two types to

[perl #131505] [@LARRY] Special case allomorph coercion everywhere

On Sat, 03 Jun 2017 21:20:49 -0700, c...@zoffix.com wrote: > (found in discussion in > https://rt.perl.org/Ticket/Display.html?id=131493 ) > > > We have some special casing for coercion of allomorphs in some > instances, which > is done so there'd be some way to force one of the two types to

[perl #131515] [PERF] Performance loss in some commits

# New Ticket Created by Zoffix Znet # Please include the string: [perl #131515] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/Ticket/Display.html?id=131515 > Recently, we have had about ~2.7% overall performance loss, when running

[perl #126950] [BUG] IO::Path.perl produces incorrect expression structure

On Thu, 17 Dec 2015 09:13:52 -0800, zef...@fysh.org wrote: > IO::Path.perl produces output of the general form > $a.IO(:SPEC($b),:CWD($c)), but it turns out that this expression doesn't > actually replicate the SPEC and CWD attributes: > > > "foo".IO(:SPEC(IO::Spec::Unix), :CWD("/bar")).perl >

[perl #126950] [BUG] IO::Path.perl produces incorrect expression structure

On Thu, 17 Dec 2015 09:13:52 -0800, zef...@fysh.org wrote: > IO::Path.perl produces output of the general form > $a.IO(:SPEC($b),:CWD($c)), but it turns out that this expression doesn't > actually replicate the SPEC and CWD attributes: > > > "foo".IO(:SPEC(IO::Spec::Unix), :CWD("/bar")).perl >

Re: [perl #131492] Camelia produces different error message from commandline

As a kibitzer, I tried that with "This is Rakudo version 2017.04.3 built on MoarVM version 2017.04-53-g66c6dda implementing Perl 6.c". and got: perl6 –e "my \foo = Callable but role:: { };" Could not open –e. Failed to stat file: no such file or directory while: perl6 -e "say 'boo'" boo worked

[perl #126940] [BUG] errors for very large right shifts

On Wed, 16 Dec 2015 18:34:42 -0800, zef...@fysh.org wrote: > It seems to be intended (though it's not documented) that long bit shifts > produce the mathematically correct answer: > > > 123 +> (1 +< 10) > 0 > > but for some particularly large right shift distances, this doesn't work: > > > 123

[perl #126940] [BUG] errors for very large right shifts

On Wed, 16 Dec 2015 18:34:42 -0800, zef...@fysh.org wrote: > It seems to be intended (though it's not documented) that long bit shifts > produce the mathematically correct answer: > > > 123 +> (1 +< 10) > 0 > > but for some particularly large right shift distances, this doesn't work: > > > 123

Re: [perl #131492] Camelia produces different error message from commandline

> Something bit you; note that you are not using "-e" but "–e" (U+2013 EN DASH). > Right, the consequence of cutting & pasting. It's interesting that the error message on the corrected version is unlike either of the original examples.

Re: [perl #131492] Camelia produces different error message from commandline

> Something bit you; note that you are not using "-e" but "–e" (U+2013 EN DASH). > Right, the consequence of cutting & pasting. It's interesting that the error message on the corrected version is unlike either of the original examples.

[perl #131515] [PERF] Performance loss in some commits

On Mon, 05 Jun 2017 13:28:00 -0700, elizabeth wrote: > Generally, we don’t care about performance once we have an > unrecoverable exception that needs to be reported. If the stresstest > regression is caused by trying to do Levenstein on method names (which > can be a lot on some objects), then

[perl #131515] [PERF] Performance loss in some commits

On Mon, 05 Jun 2017 13:28:00 -0700, elizabeth wrote: > Generally, we don’t care about performance once we have an > unrecoverable exception that needs to be reported. If the stresstest > regression is caused by trying to do Levenstein on method names (which > can be a lot on some objects), then

Re: [perl #126940] [BUG] errors for very large right shifts

Zoffix Znet via RT wrote: >For record, all three of the problematic ones now throw. Is that the >desired behaviour? Not the desired behaviour, no. It's a massive improvement over giving the wrong answer, and arguably fixes the bug qua bug, but it's still less than awesome. It would be easy (and

Re: [perl #126940] [BUG] errors for very large right shifts

Zoffix Znet via RT wrote: >For record, all three of the problematic ones now throw. Is that the >desired behaviour? Not the desired behaviour, no. It's a massive improvement over giving the wrong answer, and arguably fixes the bug qua bug, but it's still less than awesome. It would be easy (and

Re: [perl #131492] Camelia produces different error message from commandline

On Mon, Jun 5, 2017 at 5:32 PM, Parrot Raiser <1parr...@gmail.com> wrote: > perl6 –e "my \foo = Callable but role:: { };" Something bit you; note that you are not using "-e" but "–e" (U+2013 EN DASH). -- brandon s allbery kf8nh sine nomine associates

Re: [perl #131492] Camelia produces different error message from commandline

On Mon, Jun 5, 2017 at 5:32 PM, Parrot Raiser <1parr...@gmail.com> wrote: > perl6 –e "my \foo = Callable but role:: { };" Something bit you; note that you are not using "-e" but "–e" (U+2013 EN DASH). -- brandon s allbery kf8nh sine nomine associates

Re: [perl #131515] [PERF] Performance loss in some commits

> On 5 Jun 2017, at 19:30, Zoffix Znet (via RT) > wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string: [perl #131515] > # in the subject line of all future correspondence about this issue. > #

Re: [perl #131515] [PERF] Performance loss in some commits

> On 5 Jun 2017, at 19:30, Zoffix Znet (via RT) > wrote: > > # New Ticket Created by Zoffix Znet > # Please include the string: [perl #131515] > # in the subject line of all future correspondence about this issue. > #

[perl #131492] Camelia produces different error message from commandline

On Fri, 02 Jun 2017 23:29:40 -0700, ben-goldb...@hotmail.com wrote: > On #perl6 IRC, I typed this: > > m: my \foo = Callable but role :: { }; > <+camelia> rakudo-moar ef9872: OUTPUT: «X::Method::NotFound exception > produced no message␤ in block at line 1␤␤» > > If, at my command prompt, I

[perl #131492] Camelia produces different error message from commandline

On Fri, 02 Jun 2017 23:29:40 -0700, ben-goldb...@hotmail.com wrote: > On #perl6 IRC, I typed this: > > m: my \foo = Callable but role :: { }; > <+camelia> rakudo-moar ef9872: OUTPUT: «X::Method::NotFound exception > produced no message␤ in block at line 1␤␤» > > If, at my command prompt, I

Re: [perl #131492] Camelia produces different error message from commandline

As a kibitzer, I tried that with "This is Rakudo version 2017.04.3 built on MoarVM version 2017.04-53-g66c6dda implementing Perl 6.c". and got: perl6 –e "my \foo = Callable but role:: { };" Could not open –e. Failed to stat file: no such file or directory while: perl6 -e "say 'boo'" boo worked

Re: [perl #131492] Camelia produces different error message from commandline

I just noticed the - was a different length, so I changed it, et voila: perl6 -e "my \foo = Callable but role:: { };" ===SORRY!=== Error while compiling -e Undeclared routine: role used at line 1. Did you mean 'roll'? On 6/5/17, Parrot Raiser <1parr...@gmail.com> wrote: > As a kibitzer, I

Re: [perl #131481] [BUG] No perl6-debug

If rakudobrew is only for core hackers, then why is it on the rakudo site as the best way to get rakudo? As for documentation, I googled perl6 debug and find perl6-debug. I am informed that it is available when perl6 is installed. I now know that perl6-debug-m is bit rotted, but I quote from 5

[perl #131481] [BUG] No perl6-debug

On Mon, 05 Jun 2017 14:45:26 -0700, rnhainswo...@gmail.com wrote: > If rakudobrew is only for core hackers, then why is it on the rakudo > site as the best way to get rakudo? Is that on rakudo.org? I see some mention of rakudobrew on http://rakudo.org/how-to-get-rakudo/ pending updates to the