The best thing to do is sit down and read
a lot of
reviews. I was too ambiguous about code ... book
reviews do not need to include code, but i think that
module reviews benefit from good, easy to digest, cohesive
code. There really are no rules for writing reviews for the
Monastery, that's why i recommend that you read a lot of
them and decide for yourself. As a bonus, you will learn
a lot more than you probably ever wanted to know about
Perl. ;) If you would like some recommendations, then check
out
ybiC's
review of Data Munging and
davorg's
review of the mod_perl Cookbook.
Steve_p even managed to get away with a
review on a Java book. :D
And as always, when in doubt, post your review to your
scratch pad and politely ask the monks
hanging around the Chatterbox to critique it.
jeffa
L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)
