I am still trying to figure out what the code is doing. But i noticed you opened short_sequence_* for output and then use it for read?

You want to either close that file before you read or don't write out, just put it in an array (if the file is small enough)

Can you try  close (OUT_NORM) or die $!; before you call make_files();?

-SK

update: Here is an example on what will happen if try to re-read non-closed files

#!/usr/bin/perl -w
open (OUT, ">junk.txt") or die $!;

print OUT ("hi\n") for (1..3);
close(OUT) or die $!;  
open (IN,"<junk.txt");
print while(<IN>);
close(IN) or die $!;

[download]

the output right now is 

hi
hi
hi

[download]

however if you comment out close(OUT) you will not see any output.

hopefully this fixes your issue!

In reply to Re: What is the problem of subroutine "make_file" in my code? by sk
in thread What is the problem of subroutine "make_file" in my code? by everwood

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.