, your tone seems to disparage my intentions.
If you read my post as a request to change Perl then I
was not clear, I would just like that effect. Given the
nature of the problem the easiest technically correct code-fix probably is to hack
the perl source and add a check and fail to where package
statements are handled. That would
likely be a fairly localized patch.
Collision of module names is a issue. In my code, client
invited to partition a problem by creating sub-classes. It is very possible that the same namespace
could be inadvertently reused. I am not trying to enforce
the common conventions of a Good Practice(TM).
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.