That is under-specified. What is the table layout? Spaces only or tabs? With TAB's, have a loog at Text::CSV and it's faster parent Text::CSV_XS. If spaces only, you have a problem, as the first line is not aligned with the rest. If it were, pack/unpack would most likely be of help:

# Example using split on multiple spaces
open my $fh, "<", "INPUT";
while (<$fh>) {
    $. < 100 and next;
    chomp;
    my ($typ, $gid, $org, $lvl) = split m/\s\s+/ => $_;
    say "$. $gid, $lvl";
    }
close $fh;

# Example with TAB's
use Text::CSV_XS;
open my $fh, "<", "INPUT";
my $csv = Text::CSV_XS->new ({ binary => 1, sep_char => "\t", auto_dia
+g => 1 });
while (my $line = $csv->getline ($fh)) {
    $csv->record_number < 100 and next;
    my ($typ, $gid, $org, $lvl) = @{$line};
    say "$. $gid, $lvl";
    }
close $fh;

# Example with unpack (I manually aligned the header line)
open my $fh, "<", "INPUT";
while (<$fh>) {
    $. < 100 and next;
    chomp;
    my ($typ, $gid, $org, $lvl) = unpack "A25 A10 A26 A*" => $_;
    say "$. $gid, $lvl";
    }
cloase $fh;
[download]

You have wrote an implementation of it but i asked to check my pseudocode if it is correct or not?

(pseudo)code cannot be validated if the (input)requirements are not clear.

So, sorry if I took the fun part out of your assignment, but this is how I try to make sense of pseudo-code.

What pseudo-code also doesn't clearly define is the output-format and validation of input. Also things to think about (also in pseudo-code).

As I personally "do" a lot of perl, I think perl, so my pseudo-code *is* perl. Be it with typoes and syntax errors, but perl (when using strict and warnings) will point me at those for me to fix.


Enjoy, Have FUN! H.Merijn

IF line >= 100
[download]

I often use Perl itself as pseudocode. I call subroutines which do not exist yet, omit initialization and formats, make my best guess at syntax that I am not sure of, etc. Then I compile it and fix the syntax errors. Then I add details until I have a working program.

Like BillKSmith I tend to go straight to sketch code rather than something that looks a little like code but doesn't morph directly into anything in particular. That gives me a head start in writing the actual code and also helps me think about testing.

So for your sample I might write something like:

use strict;
use warnings;

my @tableLines = FetchTable();

for my $tableLine (@tableLines) {
    next if $tableLine->{expressionLevel} >= 100;
    
    print "TableLine->{geneID} TableLine->{expressionLevel}\n";
}
[download]

which is at least as good as the pseudo code at elaborating the idea for the program, is insignificantly harder to set down, and focuses attention on important elements of the program that are unclear in the pseudo code (what does PRINT geneID IN table really mean?). In the real world these days tools like pseudo code and flow diagrams (for code) are seldom used and are of limited utility compared to things like test driven development.

If this is a homework exercise it may still be worth sketching the program as I have done above and then "reverse engineer" the pseudo code from it. If my sketch code captures your intent then the pseduo code you have as it stands is fine.