Ignoring
moritz's very good suggestion, you could perform a naive search by storing the contents of the first file in an
array of arrays. This would end up looking something like (untested):
my @file1 = ();
open(FILE, @ARGV[0]) ||
die ("could not open file @ARGV[0]\n");
while (my $line = <FILE>) {
chomp $line;
my ($chr, $start, $stop) = split(/\t/, $line);
push @file1, [$chr, $start, $stop];
}
close FILE;
open(FILE, @ARGV[1])||die ("could not open file @ARGV[1]\n");
while(<FILE>){
($Gene,$Chrom,$ModStart,$ModEnd,$Strand,$ExonCount,$SizeKB)= s
+plit;
# foreach (line in genes.db){ # I don't know what to put here
+.
foreach my $line (@file1){
my ($chr, $start, $stop) = @$line;
if ($chr eq $Chrom && $start gt $ModStart && $end lt $ModE
+nd){
$Count++;
print ;($Gene,$Chrom,$ModStart,$ModEnd,$Strand,$ExonCount,
+$SizeKB,$Count)
}
}
Note that your original concept had some scoping issues.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.