You don't saywhy it needs to be that way.

If your two arrays are the pre-requisite for other code, then go for it. But I think it would be better to use a hash, with the header as the key and the sequence as the value. If you might have multiple instances of a header, use arrays of sequences as the values:

while ( my $header = <$fh> ) {
  my $sequence = <$fh>;
  chomp ( $header, $sequence );
  $data{$header} = $sequence;
# or
  push @{ $data{header} }, $sequence;

# to read

print "$_ -> $data{$_}.\n" for sort keys %data;

# or for the hash of arrays

for my $key ( sort keys %data ) {
   print "$key : $_.\n" for @ { $data{$key} };
}

[download]

As Occam said: Entia non sunt multiplicanda praeter necessitatem.

In reply to Re: Bioinformatic task by TomDLux
in thread Bioinformatic task by uvnew

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.