I have to write a perl script to go over the C code base and identify all the functions in each file and replace each function name with a keyword, for example, i have a file name 1.c 
int func1(struct commandId)
{
  do();
  return ( SUCCESS );
}
void func2(struct commandId)
{
  do();
  return ( SUCCESS );
}
float func3(struct commandId)
{
  do();
  return ( SUCCESS );
}

[download]
My intention is to replace func1, func2, func3 with func1_main, func2_main, func3_main....I see lot of advices, but quite confused as I am very new to PERL as to which method i should follow. The code base is big and there are lot of files and other open close braces in if else statements etc.., so, i would like to know any parser that exist in PERL to do this intended function.

In reply to Identifying functions in a c file and replacing with a keyword by ijalab

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.