You've read all the perldocs, tutorials and can quote verbatim from the Camel book. Even so you come across sections that don't make immediate sense or you'll think "I'm never going to use that!".

Like in perlre:

 (??{ code })
    ...
    This is a "postponed" regular subexpression.  The
    "code" is evaluated at run time, at the moment this
    subexpression may match. The result of evaluation is
    considered as a regular expression and matched as if
    it were inserted instead of this construct.
[download]

"What would I use that for?"

Well, I came across a use yesterday. I find that B<some bold text> is easier to read than <b>some bold text</b>. Hence I wanted to use that on my website to make writing their web pages easier for my kids & wife. I didn't need the full POD syntax, so here it is: the (over)simplified one-line POD-2-HTML text marker.

   1 while s!([BUI])(<+)\s*(.*?)\s*(??{'>' x length $2})!<$1>$3</$1>!;
[download]

It translates:

   "B<<< I<< U<bold underlined text> >> >>>"
[download]

to

  <B><I><U>bold underlined text</U></I></B>
[download]

(I know that in this case the HTML version is actually more readable than the bracketed version, but I just wanted to show that it handles stacked markup.)

Regex explanation:

my $pod2html = qr/
  ([BUI])                  # start of formatting pattern
  (<+)                     # collect opening braces
  \s*(.*?)\s*              # collect text, without border space
  (??{'>' x length($2)})   # match same number of closing braces
/x;
[download]

By using a hash lookup, this is easily expanded to include all kinds of translations.

---

---

• 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.