After thinking about it some, I don't like the way some of the solutions behave when you have \n at the end or beginning. To me, it would make more sense to ignore these. You can do that as a separate step, or integrate it in to the regex: 
my $paragraphs = $comments_to_add =~
    s&(?=.*\S|\A)\s*(.*?)\s*?(?:\n(?!\r?\n)|\z)&<p>$1</p>&g;

[download]
This assumes you want <p></p> even around an empty comment. If that's not the case, it's easier: 
my $paragraphs = $comments_to_add =~
    s&\s*(.+?)\s*?(?:\n(?!\r?\n)|\z)&<p>$1</p>&g;

[download]
I was dissatisfied with how complicated this turned out. If anyone has suggestions for making it simpler, I'd love to see.

In reply to Re: Re: Parsing and adding to a "variable". by ysth
in thread Parsing and adding to a "variable". by powerhouse

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.