Re: [perl #128632] [BUG] get freezes terminal on x64 Windows implementation

2016-08-25 Thread Josh Helzer

Hello,

Unfortunately, I'm getting the same freeze/no echo behavior upon 
executing *my $in = get;* on the REPL.  This obtains with perl6 running 
under cmd.exe, cmd.exe with Administrative privileges, and with 
powershell.exe.


Versions:

 * Rakudo version 2016.07.1 built on MoarVM version 2016.07
   implementing Perl 6.c;
 * Windows Server 2012 R2 Standard


However!  I was inspired by an email from Naoum Hankache 
 I just now read regarding an error I encountered 
while reading his tutorial.  His discovery was that putting the same 
commands within a script - rather than entering them at the REPL - fixed 
the problem.  The same is true here:  If I create a simple test file, e.g.:


   my $in = get;
   say $in;

and run that, then input echoes as expected,  terminates input, 
and the string is successfully echoed.



On 08/16/2016 11:34 AM, Zoffix Znet via RT wrote:

Hi,

Were you able to try the latest Rakudo Star? and see if the problem is still 
there? http://rakudo.org/downloads/star/rakudo-star-2016.07-x86_64%20(JIT).msi

I'm not able to reproduce this on Windows 7, even with the 2016.04 version. The 
code starts and waits for input. I type it in, press Enter and the program 
returns just fine, with my input echoed on the screen as I type it.








Re: [perl #128632] [BUG] get freezes terminal on x64 Windows implementation

2016-07-18 Thread Josh Helzer

What is the more recent version for Windows that I missed?

On 07/18/2016 08:21 AM, Zoffix Znet via RT wrote:

Thanks for the report.

Based on your description, it seems like the issue has already been resolved in 
more recent releases.

Would you, please, describe what needs to be done in order for this ticket to 
be considered as resolved?





Re: [perl #128632] [BUG] get freezes terminal on x64 Windows implementation

2016-07-17 Thread Parrot Raiser
Looking at the version numbers, 2016.04 on vs 2016.06 suggests it
might have been fixed. Can you get the later version on the Windows
box?

On 7/16/16, Josh Helzer  wrote:
> # New Ticket Created by  Josh Helzer
> # Please include the string:  [perl #128632]
> # in the subject line of all future correspondence about this issue.
> # https://rt.perl.org/Ticket/Display.html?id=128632 >
>
>
> Hello.
>
> On Rakudo version 2016.04 built on MoarVM version 2016.04 implementing Perl
> 6.c on x64 Windows Server 2012 R2, running perl6 within cmd.exe and
> entering the following
>
> my $in = get;
>
> results in an apparently frozen interpreter:  Input is not echoed, nor does
> entering any number of newlines do anything, nor Ctrl+d, nor Ctrl+z, nor
> even Ctrl+c.
>
> I get similar unresponsive behavior with prompt, too.
>
> Neither issue occurs if I use Rakudo version 2016.06-281-gcd42657 built on
> MoarVM version 2016.06-9-g8fc21d5 implementing Perl 6.c on x64 Ubuntu
> 16.04.
>


[perl #128632] [BUG] get freezes terminal on x64 Windows implementation

2016-07-16 Thread via RT
# New Ticket Created by  Josh Helzer 
# Please include the string:  [perl #128632]
# in the subject line of all future correspondence about this issue. 
# https://rt.perl.org/Ticket/Display.html?id=128632 >


Hello.

On Rakudo version 2016.04 built on MoarVM version 2016.04 implementing Perl
6.c on x64 Windows Server 2012 R2, running perl6 within cmd.exe and
entering the following

my $in = get;

results in an apparently frozen interpreter:  Input is not echoed, nor does
entering any number of newlines do anything, nor Ctrl+d, nor Ctrl+z, nor
even Ctrl+c.

I get similar unresponsive behavior with prompt, too.

Neither issue occurs if I use Rakudo version 2016.06-281-gcd42657 built on
MoarVM version 2016.06-9-g8fc21d5 implementing Perl 6.c on x64 Ubuntu 16.04.