> But now I would like to port it to bash ... bash doesn't have regex search and replace but sed does

Why do you want to port it to bash?

The wise coder won't shell out to grep, awk or sed
Since no JAPH would be seen doing that, dead

-- from hippo's classic poem The wise coder

Unix shell versus Perl argues strongly that it's better to write everything in Perl, rather than a motley mix of shell, grep, sed, awk and so on -- so please tell us why you want to port a working perl script to bash.

I've added your question to my list of Shell to Perl References. 

👁️🍾👍🦟

In reply to Re: Commify function regex in Perl vs sed by eyepopslikeamosquito
in thread Commify function regex in Perl vs sed by harangzsolt33

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.