I think there is a very good and a very bad side to this, although the bad side can be mitigated.

The Bad side

The bad side that I see, as others have pointed out, is that someone may pose a pure regex question, when they should actually be asking a more general question. A simple example would be something like why doesn't this regex match this deeply nested xml fragment - In this case someone could easily recognise the real problem, move the node and point the monk to XML::Twig or similar. Not all non-re questions would be as easily identified though, and people might just hedge their bets in phrasing questions thus removing the benefit of having an re specific area.

The Good side

On the other hand, a big plus that I see is that a regex specific area would be relevant to non-Perl people. I can envision regex.perlmonks.org becomming the defacto place for all regex QA, thus helping raise the profile of perlmonks and Perl (which nicely segues to the node: "Popularity of Perl vs. availability of Perl developers").

On balance I think it's worth a try. If it turns out to be a bad idea, all the nodes can just be re-homed into SoPW and the area removed.


In reply to Re: New section for Regex Q's? by aufflick
in thread New section for Regex Q's? by xdg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.