«

Hi,

This is the pattern from a C function:

<<snip>>
void foo(....)
{
.....
}
<<snip>>

Given the function name, is there an easy way to extract the function text from a C file in Perl?

Thanks in advance,
Jose Luis

On 09/29/2012 11:56 AM, wrote:
> Hi,
>
> This is the pattern from a C function:
>
> <<snip>>
> void foo(....)
> {
> ....
> }
> <<snip>>
>
> Given the function name, is there an easy way to extract the function text from a C file in Perl?

In general: No.
You need a /scanner/parser for C for that.

Josef

El sábado, 29 de septiembre de 2012 16:30:24 UTC+2, Josef Moellers escribió:
> On 09/29/2012 11:56 AM, jose.luis.fdez.diaz at ..... gmail.com wrote:
>
> > Hi,
>
> >
>
> > This is the pattern from a C function:
>
> >
>
> > <<snip>>
>
> > void foo(....)
>
> > {
>
> > ....
>
> > }
>
> > <<snip>>
>
> >
>
> > Given the function name, is there an easy way to extract the function text from a C file in Perl?
>
>
>
> In general: No.
>
> You need a /scanner/parser for C for that.
>
>
>
> Josef

Thanks for your answer Josef.

Perhaps this is possible. Given this pattern:

<<snip>>
{
{
....
}

{
....

{
...
}

....

}
}
<<snip>>

Is there and easy way to get the text between the external braces?


Regards,
Jose Luis

In article <1b62de6b-931a-481d-bce1->,
<> wrote:

> Hi,
>
> This is the pattern from a C function:
>
> <<snip>>
> void foo(....)
> {
> ....
> }
> <<snip>>
>
> Given the function name, is there an easy way to extract the function text
> from a C file in Perl?

I have used the Text::Balanced module for this kind of thing in the
past.

--
Jim Gibson

On 2012-10-01, Eli the Bearded <*@eli.users.panix.com> wrote:
> In comp.lang.perl.misc, <> wrote:
>> Given the function name, is there an easy way to extract the function
>> text from a C file in Perl?
>
> You are in a world of hurt if the programmer hates you.
>
>:r macro.c
> #include <stdio.h>
>
> #define PROGRAMMER_HATES_YOU }

Note that such buffoonery in the source will also likely defeat numerous
popular programming tools like cscope, mkid and ctags. Oh, not to mention
syntax highlighting and automatic code indentation in your text editor, and the
reporting of function names in context diff hunks.

So that should really be:

#define PROGRAMMER_HATED_BY_TEAM_CUSTOMERS_WIFE_KIDS_DOG )