in reply to Profiling Embedded Perl

Whether this is helpful or not you'll have to tell me, but every use of eval_pv() a quick grep turned up, it had 2 parameters not 1. 

eval_pv
Tells Perl to eval the given string and return an SV* result.

NOTE: the perl_ form of this function is deprecated.

        SV*     eval_pv(const char* p, I32 croak_on_error)

[download]

HTH.

Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
Hooray!

Replies are listed 'Best First'.
Re: Re: Profiling Embedded Perl
by Anonymous Monk on Jan 07, 2004 at 15:25 UTC
    Thanks, but what I wrote was very pseudo code. I'm not having any trouble eval'ing perl code, just profiling it.

    -nik

[reply]

      Okay. T'was just something that stood out.

      Just another thought, but would it be easier to profile the code your eval'ing, from a standard perl script rather via embedded perl?

      Examine what is said, not who speaks.
      "Efficiency is intelligent laziness." -David Dunham
      "Think for yourself!" - Abigail
      Hooray!
[reply]
        I wish, but no. The code has callbacks into C++, so we're going C++->Perl->XS->C++. In essence, we're using perl as a scripting language in our app. Doesn't work too well w/o the app ;)

        Thanks for your help, tho.

        -nik

[reply]

In Section Seekers of Perl Wisdom