Prossibly not useable (this has the stench of homework about it) but considering the problem domain BioPerl would be the first thing to check out. Even if it is homework you're supposed to build from scratch you may be able to gain inspiration, but judging by the orphaned method call on a $mySeq instance its use could be expected.
And mentioning because it jumped out at me: ALWAYS CHECK THE RETURN FROM open CALLS. You did your first but you didn't creating some of your output file(s) which means that's inevitably going to silently fail some time and you're then going to be stuck trying to track down what's gone wrong when that happens (and it will; Murphy sez so). Even your trick conditionally opening the last output it might be useful to print an informational diagnostic message to indicate why you're not writing to the file rather than STDOUT.
if( not $succ ) {
print STDERR qq{Unable to append to '$file', using STDOUT: $!\n};
$fh = \*STDOUT;
}
The cake is a lie.
The cake is a lie.
The cake is a lie.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|