My working perl code on my old Windows7 laptop no longer works on my new laptop running Windows10

Old laptop is running Strawberry Perl v5.26.1, and I run the scripts in Git Bash. I'm switching over to my new laptop running Windows10, using Strawberry Perl v25.6.2 in Git Bash. On the new laptop, the codes' first user interaction *should* ask for, and process, a number from the user but it appears to pause. IF I hit Enter if proceeds in the code without processing the user's input

use strict ; use warnings ; use diagnostics ; my $index ; my $Instance ; my $numClients ; my @ClientList ; use Scalar::Util qw(looks_like_number) ; print "How many Clients are you entering? \n" ; # 5 $numClients = <STDIN> ; chomp($numClients) ; if ( !looks_like_number($numClients) ) { print " Your input is NOT a numeric\n" ; exit(1) ; }

any help is appreciated, thanks O Wise Ones


In reply to not working in Win10 by Boschman

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.