Definitely not in order of importance, and NOT to excoriate you (in fact, perhaps betraying bits 'n pieces of mine own ignorance), but
- Why use "-w" and "use warnings;" and why NOT "use strict;" Hint: you'll find a wealth of information by simply searching or supersearching.
- Naming of variables: "$media" for example -- ah, paper vs. canvas, vs. one-inch-tape vs. 8 inch floppies? BRRRRRT! Suggestion: use accurately meaningful var names.
- "Unknown file format" -- I don't think it's going to be an "unknown file format" that sends flow to the die; I think it's going to be a failure to match a string which includes, somewhere within it, the characters "WMS." Recommendation: make your messages mean what they say and say what they mean!
What this smells like is cargo culting and cut-and-pasting without a clear understanding of what the ancestor code did or how it worked.
And, for us to help, we surely need a somewhat clearer exposition -- a snippet, sample -- of the logfile whose format is unknown to us.
Please UPDATE your question... and please read How do I post a question effectively? both of which will help us to help you.
-
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.
|
