I don't see that its good for anyone to advocate anything blindly. Perl is not the only solution, and in some cases, it is the wrong solution. I enjoy programming in Perl too, but I don't want to live next to a nuclear power plant where the control systems are written in Perl.
mirod's point is that there are often solutions to problems with XML other than "just use XSLT". Many of the modules listed above often can handle the problems seen in SOPW. There, people are looking for suggestions or sample code to solve problems that they are running into. He's not blindly advocating Perl as the only solution, he would just like some code from people advocating an XSLT-based solution.
-
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.
|
