This relates a question about how CPAN assigns names: XML::Parser, for example, defines a namespace which could represent one of any of the following:
- A module that uses its namespace for private modules to comprise a larger solution.
- A package that defines a general topic- modules within the namespace generally relate to the topic, but are otherwise unrelated to each other.
- An interface whose namespace contains implementation modules.
Perl doesn't have any explicit declaration to distinguish one approach from the other. But XML::Parser
is implemented as the last approach. And the Built_In_Styles member seems to be merely notational, not functional.
In fact, any module that shares the XML::Parser namespace can be invoked as a Style argument. I merely had to add some handler wrappers to get the desired output.
-
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.
|
