, 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).