Re^5: When to (and not to) use sv

in reply to Re^4: When to (and not to) use sv_2mortal()
in thread When to (and not to) use sv_2mortal()

This is the sort of thing that if I'm going to invest the time in learning it, I want to learn it right.

Once you get past the initial get something working stage is when it gets interesting and then frustrating.

For example, in this version of your code I've stripped out a whole bunch of macros and it still compiles clean and runs leak-free. Unsuprisingly, it is a tad quicker:

int test_perlcall( int input ) {
    dSP;  /* Declare and initialize local copy of Perl stack ptr */

    PUSHMARK(SP);
    XPUSHs(sv_2mortal(newSViv( input )));
    PUTBACK;

    if( call_pv( "return_input", G_SCALAR ) != 1 )
        croak( "Well, THAT failed to work.\n" );

    return (int)POPi; /* Inline::C handles this typemap automatically.
+ */
}
[download]

But then you start wondering why all those apparently unneeded macros are used in the samples. They obviously are required on some occasions, but when? And why?

It is answers to these questions that are much harder to obtain.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In Section Seekers of Perl Wisdom