Inherited few Perl Script with echo/sed/awk/grep commands in backticks or system. Is it best practice to convert them to Perl or to leave as it is.

IMHO, yes, definitely! See Calling External Commands More Safely for the issues with backticks, and also The problem of "the" default shell, which also names a few equivalencies.

Do we have conversion recopies ?

Well, for sed and awk there are App::s2p and App::a2p, respectively, although note the Perl code they produce isn't perfect - but it's a good starting point for conversion. As for the others, grep shouldn't be all too difficult to convert to Perl regexes, and if there's anything else, then perhaps you can name them more specifically and show examples, and perhaps we can help with those.

In reply to Re: sed/awk/grep to Perl by haukex
in thread sed/awk/grep to Perl by aartist

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.