MHonArc Users,
Since many users are using Perl 5, there is a potential conflict
when specifying MIME filters and charset filters. For example,
the current way is the following:
<mimefilters>
text/plain:mypack'filter:myfilters.pl
</mimefilters>
The problem is that a ':' is used to delimit the fields. However,
this will conflict if Perl 5 package qualifiers are used. Example:
<mimefilters>
text/plain:mypack::filter:myfilters.pl
</mimefilters>
Mhonarc will interpret the "::" as field delimiters.
My questions to you is what is a reasonable solution to the
problem? Should a new field delimiter be used? If so, what
about other resources that use ':' as a delimiter, but have
no conflict since Perl routines are not being specified (egs:
labelstyles, fieldstyles, etc). Should mhonarc try to be
intelligent and treat "::" as a package qualifer and a single
':' as a field delimiter? Leave things as-is and require
users to use the Perl 4 syntax?
Comments are welcome since changes may cause compatibility
problems with some users.
--ewh
P.S. Another questions is retaining Perl 4 compatibility still
needed? Although MHonArc will probably not take advantage of
Perl 5 OO constructs for awhile (too much rewriting at this time),
other Perl 5 enhancements may be nice to use.
----
Earl Hood | University of California: Irvine
ehood(_at_)medusa(_dot_)uci(_dot_)edu | Electronic Loiterer