Re^3: Why does this sub grab the whole hash

[davido]

@dr is not lexically scoped. The result is that each time the sub is called, unless you're reinitializing it somewhere that we're not seeing, @dr still has cruft in it from previous calls to the subroutine. It probably needs to be declared as my @dr.

$done is also not lexically scoped, but that's not as important as you're doing an assignment to it rather than an append. push is like an append for an array. If the array already has junk in it, you're just adding to what's already there.

[naturalsciences]

Oh man - enlightenment just hit me. Looked over my code and now I got how this poor array was filled over and over again with some quite random stuff in the different parts of my script. Really bad idea to use a subs like this with a globally defined array.

[moritz]

And that's why people always recommend to usestrict; -- it complains about undeclared variables, so it forces you to think about where to put the declaration. And you only put the declaration outside the subroutine if that's your conscious choice.

[AnomalousMonk]

Really bad idea to use a subs like this with a globally defined array.

It's a really bad idea to use subs (or anything else) with a globally defined, non-constant anything unless, as moritz has written, it's your conscious decision to do so — and even then I'd think twice about it.

[naturalsciences]

Changing the subs code to..

 sub revcompl {
  my (@dna) = @_;
  my @dr=();
  foreach my $segment (@dna) {
    my $revcomp = reverse($segment);
    $revcomp =~ tr/ACGTacgtMKRYBDHVmkrybdhv/TGCAtgcaKMYRVHDBkmyrvhdb/;
    push  @dr, $revcomp;
  }
  $done = join('',@dr);
  return $done;
}

Worked out well. Thank you very much. The behaviour noticed before still weirds me out, guess it's time to study some more. Any more enlightening comments on what happened there are welcome by everybody :D