Re: [perl #131076] [LTA] Rakudo sees Perl 5 code even if there is none (for $x(42), $x(50) {…})

2017-03-29 Thread Brandon Allbery
That *is* Perl 5 syntax, though; it looks like the schema

for $var (list) { ... } # the space is not required between the var and
the parenthesized list


On Wed, Mar 29, 2017 at 9:35 PM, Aleks-Daniel Jakimenko-Aleksejev <
perl6-bugs-follo...@perl.org> wrote:

> # New Ticket Created by  Aleks-Daniel Jakimenko-Aleksejev
> # Please include the string:  [perl #131076]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=131076 >
>
>
> Code:
> my $x = *²; for $x(42), $x(50) { say $_ }
>
> Result:
> ===SORRY!=== Error while compiling -e
> This appears to be Perl 5 code
> at -e:1
> --> my $x = *²; for ⏏$x(42), $x(50) { say $_ }
>



-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net


[perl #131076] [LTA] Rakudo sees Perl 5 code even if there is none (for $x(42), $x(50) {…})

2017-03-29 Thread via RT
# New Ticket Created by  Aleks-Daniel Jakimenko-Aleksejev 
# Please include the string:  [perl #131076]
# in the subject line of all future correspondence about this issue. 
# https://rt.perl.org/Ticket/Display.html?id=131076 >


Code:
my $x = *²; for $x(42), $x(50) { say $_ }

Result:
===SORRY!=== Error while compiling -e
This appears to be Perl 5 code
at -e:1
--> my $x = *²; for ⏏$x(42), $x(50) { say $_ }


[perl #131075] [BUG] harness6 runs incorrect number of tests when spec or stresstesting

2017-03-29 Thread via RT
# New Ticket Created by  Jan-Olof Hendig 
# Please include the string:  [perl #131075]
# in the subject line of all future correspondence about this issue. 
# https://rt.perl.org/Ticket/Display.html?id=131075 >


When running spectest (or stresstest) under harness6 not all files in 
spectest.data that should be run are being run. For example:

'make spectest TEST_JOBS=3', i.e. harness5 tests 1168 files

on the other hand

'make spectest HARNESS_TYPE=6 TEST_JOBS=3' only tests 1160 files

The two harnesses should test the same number of files. There's reason to 
believe that the bug hides in harness6.


Re: write string requires an object with REPR MVMOSHandle

2017-03-29 Thread Shlomi Fish
On Wed, 29 Mar 2017 12:47:58 +0200
Elizabeth Mattijsen  wrote:

> > On 29 Mar 2017, at 12:36, Shlomi Fish  wrote:
> > 
> > On Wed, 29 Mar 2017 12:10:15 +0200
> > Timo Paulssen  wrote:
> >   
> >> As part of the IOwesome grant, zoffix is going to fix this error. It's
> >> what you get when you try to write to or read from or do anything with a
> >> closed IO::Handle.
> >> 
> >> When you use "LEAVE:" you're just declaring a label called "LEAVE".
> >> There are no labels with special function, so your code is equivalent to
> >> 
> >> sub save {
> >>my $fh = open('data.txt', :w);
> >>ohai: $fh.close;
> >>$fh.print("hello\n");
> >> }
> >> 
> >> so you're opening the file, closing the file, then writing to it. That
> >> can't work, of course, but the error is also clearly LTA.
> >>   
> > 
> > Hi Timo!
> > 
> > What does "LTA" stand for in this context? One thing I learned is to avoid
> > acronyms as much as possible.  
> 
> Less Than Awesome
> 

Thanks, Liz!

> 
> 
> Liz


Re: write string requires an object with REPR MVMOSHandle

2017-03-29 Thread Elizabeth Mattijsen
> On 29 Mar 2017, at 12:36, Shlomi Fish  wrote:
> 
> On Wed, 29 Mar 2017 12:10:15 +0200
> Timo Paulssen  wrote:
> 
>> As part of the IOwesome grant, zoffix is going to fix this error. It's
>> what you get when you try to write to or read from or do anything with a
>> closed IO::Handle.
>> 
>> When you use "LEAVE:" you're just declaring a label called "LEAVE".
>> There are no labels with special function, so your code is equivalent to
>> 
>> sub save {
>>my $fh = open('data.txt', :w);
>>ohai: $fh.close;
>>$fh.print("hello\n");
>> }
>> 
>> so you're opening the file, closing the file, then writing to it. That
>> can't work, of course, but the error is also clearly LTA.
>> 
> 
> Hi Timo!
> 
> What does "LTA" stand for in this context? One thing I learned is to avoid
> acronyms as much as possible.

Less Than Awesome



Liz


Re: write string requires an object with REPR MVMOSHandle

2017-03-29 Thread Shlomi Fish
On Wed, 29 Mar 2017 12:10:15 +0200
Timo Paulssen  wrote:

> As part of the IOwesome grant, zoffix is going to fix this error. It's
> what you get when you try to write to or read from or do anything with a
> closed IO::Handle.
> 
> When you use "LEAVE:" you're just declaring a label called "LEAVE".
> There are no labels with special function, so your code is equivalent to
> 
> sub save {
> my $fh = open('data.txt', :w);
> ohai: $fh.close;
> $fh.print("hello\n");
> }
> 
> so you're opening the file, closing the file, then writing to it. That
> can't work, of course, but the error is also clearly LTA.
> 

Hi Timo!

What does "LTA" stand for in this context? One thing I learned is to avoid
acronyms as much as possible.

Regards,

Shlomi

> HTH
>   - Timo


Re: write string requires an object with REPR MVMOSHandle

2017-03-29 Thread Timo Paulssen
As part of the IOwesome grant, zoffix is going to fix this error. It's
what you get when you try to write to or read from or do anything with a
closed IO::Handle.

When you use "LEAVE:" you're just declaring a label called "LEAVE".
There are no labels with special function, so your code is equivalent to

sub save {
my $fh = open('data.txt', :w);
ohai: $fh.close;
$fh.print("hello\n");
}

so you're opening the file, closing the file, then writing to it. That
can't work, of course, but the error is also clearly LTA.

HTH
  - Timo


write string requires an object with REPR MVMOSHandle

2017-03-29 Thread Gabor Szabo
I was running the following buggy code:

sub save {
my $fh = open('data.txt', :w);
LEAVE: $fh.close;
$fh.print("hello\n");
}

save();

(note the : after the LEAVE)
Which if I am not mistaken is basically the same as:


sub save {
my $fh = open('data.txt', :w);
$fh.close;
$fh.print("hello\n");
}

save();


and I kept getting the error in the subject which greatly confused me.

Shouldn't this be something like a "print of closed filehandle" error?

Gabor