I agree with
scain. Too much granularity is not healthy for the Monastery. Let's not forget the possible trends
Seekers Of Tk/Perl Wisdom and
Seekers Of ActiveState Perl Wisdom.
If you have a problem with a RegEx in your mod_perl script, would you post it to SOPW or to SOm_pW?
An error in judgement could make your question unavailable for that willing monk who thinks you are asking for something (s)he doesn't know. And when the answer comes, it will be flagged as belonging to that category where you asked, thus hiding it from the desperate eyes of the seekers of the
other perl wisdom.
However, a welcome improvement would be a
subject tag for each node, so that we could categorize each root node by one or more subjects, making it easier to search.
Example: a request about pattern matching from %ENV in a mod_perl script could be tagged as "mod_perl, CGI, taint, input, RegEx" and the answer could be useful to any user seeking advice in one of those categories.
_ _ _ _
(_|| | |(_|><
_|
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.