Hi John, Thanx for the solution ... Please tell me how to use IO::File module instead of open function in this scenario.

Actually, it's the other way round: you are using IO::File (BTW: to render this link in the source of your node you can use [mod://IO::File]) and he suggested you to use a plain regular open. If you actually read (did you?) his post, you'll notice he gives you and explicit example about how to do so, namely:

my $inFile = q{spw623147.txt};
open my $inFH, q{<}, $inFile
   or die qq{open: $inFile: $!\n};

[download]

So, what's wrong with that?!?

BTW: if you are confused by the alternate delimiters, the use of which in this context may be exaggerate and controversial to some, that can be:

my $inFile = 'spw623147.txt';
open my $inFH, '<', $inFile or die "open: $inFile: $!\n";

[download]

In reply to Re^5: Extract the variable by blazar
in thread Extract the variable by denzil_cactus

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.