While you're at it, your lint process may want to catch that there should only be one package statement per file, and that package statement should match the filename, including path, from some entry in @INC, with directory separators becoming ::, and a .pm thrown on at the end. All of this is further convention that is usually a Good Practice (tm).
Or, you could embrace the freedom that perl gives to do what you think is right instead of what Larry thinks is right. Which means not following convention when convention is getting in the way of getting your job done. I've had cause to buck convention in the past, and your lint would probably give me problems over it. The key is to allow people to do what needs to be done, as long as they acknowledge they're doing something strange. Just like we always "use strict", but have the ability to lexically scope "no strict" (preferably with a modifier, such as 'refs').
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>
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
Want more info? How to link
or How to display code and escape characters
are good places to start.