As the (very remiss) maintainer of XML::SAX, I'm also mystified by the reports you're seeing. If XML::SAX was properly installed, then there would be at least one parser module that meets the requirements you've specified.
One way to get more information would be to have one of your early test files emit more diagnostic information via the Test::More 'diag()' function. For example, it would be interesting to know what the default parser is on those servers (the class of the value returned when XML::SAX::ParserFactory->new is called with no extra requirements). It would also help to know what is actually in the ParserDetails.ini file but the exact pathname to the file will be different on each host and working it out requires replicating the %INC gymnastics from XML::SAX.pm
-
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.
|
