Well, your articles are more as stories: you find some problem and then you tell how to solve it. It's great for mag columns but not for books.
What I would like to see is some kind of reference that goes through the best (hidden) CPAN modules and tells me the pros and contras of every one and why I should use one or another.
The focus of the book should be just to let the reader know about these pearls and to easily find the best module for his task at hand. Showing how to use the modules should not be required per se, but only to demonstrate the discussion.
-
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.
|
