Front page | perl.perl5.porters |
Postings from February 2000
Re: [PATCH 5.5.660] ExtUtils::DynaLoader dl_unload_file() patch
From:
Gurusamy Sarathy
Date:
February 29, 2000 14:35
Subject:
Re: [PATCH 5.5.660] ExtUtils::DynaLoader dl_unload_file() patch
Message ID:
200002292238.OAA02261@maul.activestate.com
On Tue, 29 Feb 2000 21:24:43 GMT, Alan Burlison wrote:
>Gurusamy Sarathy wrote:
>> >! SV *sv = get_sv("DynaLoader::dl_debug", 0);
>> >--- 28,64 ----
>> >! SV *sv = perl_get_sv("DynaLoader::dl_debug", 0);
>>
>> Why was this needed? (The preferred name is get_sv(), the long form of
>> which is Perl_get_sv(aTHX_ ...).)
>
>Not according to perlguts it isn't....
Now it is. :-) (perlapi.pod should be considered the more authoritative
reference here, and that makes the right noises.)
>> >+ Perl_call_atexit(&dl_unload_all_files, (void*)0);
>> > }
>>
>> s/Perl_// here, or it won't work with multiplicity/usethreads builds.
>
>Perl_call_atexit/call_atexit aren't documented anywhere I could find,
Do I see a volunteer? :-)
>and the only use is in perlapi.c, where it is called as
>'((CPerlObj*)pPerl)->Perl_call_atexit(fn, ptr);'
>so is that broke too?
L<perlguts/How multiple interpreters and concurrency are supported> has
an overview of the "system" for naming the functions in the API.
>> There was some doubt in my mind whether call_atexit() would do the job
>> properly. What happens if the dll has allocated SVs? The call_atexit()
>> callbacks are called after objects are destroyed but *before* the SV
>> arenas are deallocated. Do you foresee any problems from that?
>
>Pass. Does that mean that @dl_librefs will have been reclaimed?
Not unless @dl_librefs is an object.
> If so,
>the patch seems to work remarkably well considering it is popping stuff
>of a free'd AV. I don't think the dll allocating SVs has anything to do
>with it - dlclose() doesn't do any sort of cleanup [...]
OK, I think that answers my question.
>I wrote the patch based on what I thought was the consensus on the
>correct way to do this - was I mislead?
Doesn't look much like it. I just want to be sure we aren't overlooking
any sharp corners.
Sarathy
gsar@ActiveState.com
-----------------------------------8<-----------------------------------
Change 5371 by gsar@auger on 2000/02/29 22:29:36
fix pods to reflect newer canonical names for call_sv() etc.
Affected files ...
... //depot/perl/gv.c#94 edit
... //depot/perl/pod/perlapi.pod#5 edit
... //depot/perl/pod/perlcall.pod#16 edit
... //depot/perl/pod/perldiag.pod#128 edit
... //depot/perl/pod/perlembed.pod#20 edit
... //depot/perl/pod/perlguts.pod#53 edit
Differences ...
==== //depot/perl/gv.c#94 (text) ====
Index: perl/gv.c
--- perl/gv.c.~1~ Tue Feb 29 14:29:41 2000
+++ perl/gv.c Tue Feb 29 14:29:41 2000
@@ -168,7 +168,7 @@
This function grants C<"SUPER"> token as a postfix of the stash name. The
GV returned from C<gv_fetchmeth> may be a method cache entry, which is not
-visible to Perl code. So when calling C<perl_call_sv>, you should not use
+visible to Perl code. So when calling C<call_sv>, you should not use
the GV directly; instead, you should use the method's CV, which can be
obtained from the GV with the C<GvCV> macro.
@@ -333,7 +333,7 @@
These functions have the same side-effects and as C<gv_fetchmeth> with
C<level==0>. C<name> should be writable if contains C<':'> or C<'
''>. The warning against passing the GV returned by C<gv_fetchmeth> to
-C<perl_call_sv> apply equally to these functions.
+C<call_sv> apply equally to these functions.
=cut
*/
==== //depot/perl/pod/perlapi.pod#5 (text+w) ====
Index: perl/pod/perlapi.pod
--- perl/pod/perlapi.pod.~1~ Tue Feb 29 14:29:41 2000
+++ perl/pod/perlapi.pod Tue Feb 29 14:29:41 2000
@@ -341,7 +341,7 @@
This function grants C<"SUPER"> token as a postfix of the stash name. The
GV returned from C<gv_fetchmeth> may be a method cache entry, which is not
-visible to Perl code. So when calling C<perl_call_sv>, you should not use
+visible to Perl code. So when calling C<call_sv>, you should not use
the GV directly; instead, you should use the method's CV, which can be
obtained from the GV with the C<GvCV> macro.
@@ -375,7 +375,7 @@
These functions have the same side-effects and as C<gv_fetchmeth> with
C<level==0>. C<name> should be writable if contains C<':'> or C<'
''>. The warning against passing the GV returned by C<gv_fetchmeth> to
-C<perl_call_sv> apply equally to these functions.
+C<call_sv> apply equally to these functions.
GV* gv_fetchmethod_autoload(HV* stash, const char* name, I32 autoload)
==== //depot/perl/pod/perlcall.pod#16 (text) ====
Index: perl/pod/perlcall.pod
--- perl/pod/perlcall.pod.~1~ Tue Feb 29 14:29:41 2000
+++ perl/pod/perlcall.pod Tue Feb 29 14:29:41 2000
@@ -45,7 +45,7 @@
it would be a good idea to have read the following two documents -
L<perlxs> and L<perlguts>.
-=head1 THE PERL_CALL FUNCTIONS
+=head1 THE CALL_ FUNCTIONS
Although this stuff is easier to explain using examples, you first need
be aware of a few important definitions.
@@ -53,17 +53,17 @@
Perl has a number of C functions that allow you to call Perl
subroutines. They are
- I32 perl_call_sv(SV* sv, I32 flags) ;
- I32 perl_call_pv(char *subname, I32 flags) ;
- I32 perl_call_method(char *methname, I32 flags) ;
- I32 perl_call_argv(char *subname, I32 flags, register char **argv) ;
+ I32 call_sv(SV* sv, I32 flags) ;
+ I32 call_pv(char *subname, I32 flags) ;
+ I32 call_method(char *methname, I32 flags) ;
+ I32 call_argv(char *subname, I32 flags, register char **argv) ;
-The key function is I<perl_call_sv>. All the other functions are
+The key function is I<call_sv>. All the other functions are
fairly simple wrappers which make it easier to call Perl subroutines in
-special cases. At the end of the day they will all call I<perl_call_sv>
+special cases. At the end of the day they will all call I<call_sv>
to invoke the Perl subroutine.
-All the I<perl_call_*> functions have a C<flags> parameter which is
+All the I<call_*> functions have a C<flags> parameter which is
used to pass a bit mask of options to Perl. This bit mask operates
identically for each of the functions. The settings available in the
bit mask are discussed in L<FLAG VALUES>.
@@ -72,40 +72,40 @@
=over 5
-=item perl_call_sv
+=item call_sv
-I<perl_call_sv> takes two parameters, the first, C<sv>, is an SV*.
+I<call_sv> takes two parameters, the first, C<sv>, is an SV*.
This allows you to specify the Perl subroutine to be called either as a
C string (which has first been converted to an SV) or a reference to a
-subroutine. The section, I<Using perl_call_sv>, shows how you can make
-use of I<perl_call_sv>.
+subroutine. The section, I<Using call_sv>, shows how you can make
+use of I<call_sv>.
-=item perl_call_pv
+=item call_pv
-The function, I<perl_call_pv>, is similar to I<perl_call_sv> except it
+The function, I<call_pv>, is similar to I<call_sv> except it
expects its first parameter to be a C char* which identifies the Perl
-subroutine you want to call, e.g., C<perl_call_pv("fred", 0)>. If the
+subroutine you want to call, e.g., C<call_pv("fred", 0)>. If the
subroutine you want to call is in another package, just include the
package name in the string, e.g., C<"pkg::fred">.
-=item perl_call_method
+=item call_method
-The function I<perl_call_method> is used to call a method from a Perl
+The function I<call_method> is used to call a method from a Perl
class. The parameter C<methname> corresponds to the name of the method
to be called. Note that the class that the method belongs to is passed
on the Perl stack rather than in the parameter list. This class can be
either the name of the class (for a static method) or a reference to an
object (for a virtual method). See L<perlobj> for more information on
-static and virtual methods and L<Using perl_call_method> for an example
-of using I<perl_call_method>.
+static and virtual methods and L<Using call_method> for an example
+of using I<call_method>.
-=item perl_call_argv
+=item call_argv
-I<perl_call_argv> calls the Perl subroutine specified by the C string
+I<call_argv> calls the Perl subroutine specified by the C string
stored in the C<subname> parameter. It also takes the usual C<flags>
parameter. The final parameter, C<argv>, consists of a NULL terminated
list of C strings to be passed as parameters to the Perl subroutine.
-See I<Using perl_call_argv>.
+See I<Using call_argv>.
=back
@@ -121,7 +121,7 @@
=head1 FLAG VALUES
-The C<flags> parameter in all the I<perl_call_*> functions is a bit mask
+The C<flags> parameter in all the I<call_*> functions is a bit mask
which can consist of any combination of the symbols defined below,
OR'ed together.
@@ -146,7 +146,7 @@
=back
-The value returned by the I<perl_call_*> function indicates how many
+The value returned by the I<call_*> function indicates how many
items have been returned by the Perl subroutine - in this case it will
be 0.
@@ -154,7 +154,7 @@
=head2 G_SCALAR
Calls the Perl subroutine in a scalar context. This is the default
-context flag setting for all the I<perl_call_*> functions.
+context flag setting for all the I<call_*> functions.
This flag has 2 effects:
@@ -174,7 +174,7 @@
=back
-The value returned by the I<perl_call_*> function indicates how many
+The value returned by the I<call_*> function indicates how many
items have been returned by the Perl subroutine - in this case it will
be either 0 or 1.
@@ -187,7 +187,7 @@
accessible from the stack - think of the case where only one value is
returned as being a list with only one element. Any other items that
were returned will not exist by the time control returns from the
-I<perl_call_*> function. The section I<Returning a list in a scalar
+I<call_*> function. The section I<Returning a list in a scalar
context> shows an example of this behavior.
@@ -208,11 +208,11 @@
=item 2.
It ensures that all items returned from the subroutine will be
-accessible when control returns from the I<perl_call_*> function.
+accessible when control returns from the I<call_*> function.
=back
-The value returned by the I<perl_call_*> function indicates how many
+The value returned by the I<call_*> function indicates how many
items have been returned by the Perl subroutine.
If 0, then you have specified the G_DISCARD flag.
@@ -225,7 +225,7 @@
=head2 G_DISCARD
-By default, the I<perl_call_*> functions place the items returned from
+By default, the I<call_*> functions place the items returned from
by the Perl subroutine on the stack. If you are not interested in
these items, then setting this flag will make Perl get rid of them
automatically for you. Note that it is still possible to indicate a
@@ -241,7 +241,7 @@
=head2 G_NOARGS
-Whenever a Perl subroutine is called using one of the I<perl_call_*>
+Whenever a Perl subroutine is called using one of the I<call_*>
functions, it is assumed by default that parameters are to be passed to
the subroutine. If you are not passing any parameters to the Perl
subroutine, you can save a bit of time by setting this flag. It has
@@ -255,7 +255,7 @@
In fact, what can happen is that the Perl subroutine you have called
can access the C<@_> array from a previous Perl subroutine. This will
-occur when the code that is executing the I<perl_call_*> function has
+occur when the code that is executing the I<call_*> function has
itself been called from another Perl subroutine. The code below
illustrates this
@@ -284,10 +284,10 @@
type of event, specify the G_EVAL flag. It will put an I<eval { }>
around the subroutine call.
-Whenever control returns from the I<perl_call_*> function you need to
+Whenever control returns from the I<call_*> function you need to
check the C<$@> variable as you would in a normal Perl script.
-The value returned from the I<perl_call_*> function is dependent on
+The value returned from the I<call_*> function is dependent on
what other flags have been specified and whether an error has
occurred. Here are all the different cases that can occur:
@@ -295,7 +295,7 @@
=item *
-If the I<perl_call_*> function returns normally, then the value
+If the I<call_*> function returns normally, then the value
returned is as specified in the previous sections.
=item *
@@ -338,7 +338,7 @@
append any new errors to any existing value of C<$@>.
The G_KEEPERR flag is meant to be used in conjunction with G_EVAL in
-I<perl_call_*> functions that are used to implement such code. This flag
+I<call_*> functions that are used to implement such code. This flag
has no effect when G_EVAL is not used.
When G_KEEPERR is used, any errors in the called code will be prefixed
@@ -365,7 +365,7 @@
=head1 KNOWN PROBLEMS
This section outlines all known problems that exist in the
-I<perl_call_*> functions.
+I<call_*> functions.
=over 5
@@ -378,12 +378,12 @@
Specifically, if the two flags are used when calling a subroutine and
that subroutine does not call I<die>, the value returned by
-I<perl_call_*> will be wrong.
+I<call_*> will be wrong.
=item 2.
-In Perl 5.000 and 5.001 there is a problem with using I<perl_call_*> if
+In Perl 5.000 and 5.001 there is a problem with using I<call_*> if
the Perl sub you are calling attempts to trap a I<die>.
The symptom of this problem is that the called Perl sub will continue
@@ -405,7 +405,7 @@
Call_fred()
CODE:
PUSHMARK(SP) ;
- perl_call_pv("fred", G_DISCARD|G_NOARGS) ;
+ call_pv("fred", G_DISCARD|G_NOARGS) ;
fprintf(stderr, "back in Call_fred\n") ;
When C<Call_fred> is executed it will print
@@ -416,13 +416,13 @@
string will not get printed.
To work around this problem, you can either upgrade to Perl 5.002 or
-higher, or use the G_EVAL flag with I<perl_call_*> as shown below
+higher, or use the G_EVAL flag with I<call_*> as shown below
void
Call_fred()
CODE:
PUSHMARK(SP) ;
- perl_call_pv("fred", G_EVAL|G_DISCARD|G_NOARGS) ;
+ call_pv("fred", G_EVAL|G_DISCARD|G_NOARGS) ;
fprintf(stderr, "back in Call_fred\n") ;
=back
@@ -439,11 +439,11 @@
to any changes made to Perl in the future.
Another point worth noting is that in the first series of examples I
-have made use of only the I<perl_call_pv> function. This has been done
+have made use of only the I<call_pv> function. This has been done
to keep the code simpler and ease you into the topic. Wherever
-possible, if the choice is between using I<perl_call_pv> and
-I<perl_call_sv>, you should always try to use I<perl_call_sv>. See
-I<Using perl_call_sv> for details.
+possible, if the choice is between using I<call_pv> and
+I<call_sv>, you should always try to use I<call_sv>. See
+I<Using call_sv> for details.
=head2 No Parameters, Nothing returned
@@ -463,7 +463,7 @@
dSP ;
PUSHMARK(SP) ;
- perl_call_pv("PrintUID", G_DISCARD|G_NOARGS) ;
+ call_pv("PrintUID", G_DISCARD|G_NOARGS) ;
}
Simple, eh.
@@ -487,18 +487,18 @@
We aren't interested in anything returned from I<PrintUID>, so
G_DISCARD is specified. Even if I<PrintUID> was changed to
return some value(s), having specified G_DISCARD will mean that they
-will be wiped by the time control returns from I<perl_call_pv>.
+will be wiped by the time control returns from I<call_pv>.
=item 4.
-As I<perl_call_pv> is being used, the Perl subroutine is specified as a
+As I<call_pv> is being used, the Perl subroutine is specified as a
C string. In this case the subroutine name has been 'hard-wired' into the
code.
=item 5.
Because we specified G_DISCARD, it is not necessary to check the value
-returned from I<perl_call_pv>. It will always be 0.
+returned from I<call_pv>. It will always be 0.
=back
@@ -534,7 +534,7 @@
XPUSHs(sv_2mortal(newSViv(b)));
PUTBACK ;
- perl_call_pv("LeftString", G_DISCARD);
+ call_pv("LeftString", G_DISCARD);
FREETMPS ;
LEAVE ;
@@ -578,11 +578,11 @@
stack pointer. Even if you aren't passing any parameters (like the
example shown in the section I<No Parameters, Nothing returned>) you
must still call the C<PUSHMARK> macro before you can call any of the
-I<perl_call_*> functions--Perl still needs to know that there are no
+I<call_*> functions--Perl still needs to know that there are no
parameters.
The C<PUTBACK> macro sets the global copy of the stack pointer to be
-the same as our local copy. If we didn't do this I<perl_call_pv>
+the same as our local copy. If we didn't do this I<call_pv>
wouldn't know where the two parameters we pushed were--remember that
up to now all the stack pointer manipulation we have done is with our
local copy, I<not> the global copy.
@@ -634,7 +634,7 @@
=item 7.
-Finally, I<LeftString> can now be called via the I<perl_call_pv>
+Finally, I<LeftString> can now be called via the I<call_pv>
function.
=back
@@ -672,7 +672,7 @@
XPUSHs(sv_2mortal(newSViv(b)));
PUTBACK ;
- count = perl_call_pv("Adder", G_SCALAR);
+ count = call_pv("Adder", G_SCALAR);
SPAGAIN ;
@@ -694,23 +694,23 @@
The only flag specified this time was G_SCALAR. That means the C<@_>
array will be created and that the value returned by I<Adder> will
-still exist after the call to I<perl_call_pv>.
+still exist after the call to I<call_pv>.
=item 2.
The purpose of the macro C<SPAGAIN> is to refresh the local copy of the
stack pointer. This is necessary because it is possible that the memory
allocated to the Perl stack has been reallocated whilst in the
-I<perl_call_pv> call.
+I<call_pv> call.
If you are making use of the Perl stack pointer in your code you must
always refresh the local copy using SPAGAIN whenever you make use
-of the I<perl_call_*> functions or any other Perl internal function.
+of the I<call_*> functions or any other Perl internal function.
=item 3.
Although only a single value was expected to be returned from I<Adder>,
-it is still good practice to check the return code from I<perl_call_pv>
+it is still good practice to check the return code from I<call_pv>
anyway.
Expecting a single value is not quite the same as knowing that there
@@ -776,7 +776,7 @@
XPUSHs(sv_2mortal(newSViv(b)));
PUTBACK ;
- count = perl_call_pv("AddSubtract", G_ARRAY);
+ count = call_pv("AddSubtract", G_ARRAY);
SPAGAIN ;
@@ -839,7 +839,7 @@
XPUSHs(sv_2mortal(newSViv(b)));
PUTBACK ;
- count = perl_call_pv("AddSubtract", G_SCALAR);
+ count = call_pv("AddSubtract", G_SCALAR);
SPAGAIN ;
@@ -907,7 +907,7 @@
XPUSHs(svb);
PUTBACK ;
- count = perl_call_pv("Inc", G_DISCARD);
+ count = call_pv("Inc", G_DISCARD);
if (count != 0)
croak ("call_Inc: expected 0 values from 'Inc', got %d\n",
@@ -921,12 +921,12 @@
}
To be able to access the two parameters that were pushed onto the stack
-after they return from I<perl_call_pv> it is necessary to make a note
+after they return from I<call_pv> it is necessary to make a note
of their addresses--thus the two variables C<sva> and C<svb>.
The reason this is necessary is that the area of the Perl stack which
held them will very likely have been overwritten by something else by
-the time control returns from I<perl_call_pv>.
+the time control returns from I<call_pv>.
@@ -964,7 +964,7 @@
XPUSHs(sv_2mortal(newSViv(b)));
PUTBACK ;
- count = perl_call_pv("Subtract", G_EVAL|G_SCALAR);
+ count = call_pv("Subtract", G_EVAL|G_SCALAR);
SPAGAIN ;
@@ -1031,7 +1031,7 @@
Note that the stack is popped using C<POPs> in the block where
C<SvTRUE(ERRSV)> is true. This is necessary because whenever a
-I<perl_call_*> function invoked with G_EVAL|G_SCALAR returns an error,
+I<call_*> function invoked with G_EVAL|G_SCALAR returns an error,
the top of the stack holds the value I<undef>. Because we want the
program to continue after detecting this error, it is essential that
the stack is tidied up by removing the I<undef>.
@@ -1061,18 +1061,18 @@
This example will fail to recognize that an error occurred inside the
C<eval {}>. Here's why: the call_Subtract code got executed while perl
was cleaning up temporaries when exiting the eval block, and because
-call_Subtract is implemented with I<perl_call_pv> using the G_EVAL
+call_Subtract is implemented with I<call_pv> using the G_EVAL
flag, it promptly reset C<$@>. This results in the failure of the
outermost test for C<$@>, and thereby the failure of the error trap.
-Appending the G_KEEPERR flag, so that the I<perl_call_pv> call in
+Appending the G_KEEPERR flag, so that the I<call_pv> call in
call_Subtract reads:
- count = perl_call_pv("Subtract", G_EVAL|G_SCALAR|G_KEEPERR);
+ count = call_pv("Subtract", G_EVAL|G_SCALAR|G_KEEPERR);
will preserve the error and restore reliable error handling.
-=head2 Using perl_call_sv
+=head2 Using call_sv
In all the previous examples I have 'hard-wired' the name of the Perl
subroutine to be called from C. Most of the time though, it is more
@@ -1095,23 +1095,23 @@
char * name
CODE:
PUSHMARK(SP) ;
- perl_call_pv(name, G_DISCARD|G_NOARGS) ;
+ call_pv(name, G_DISCARD|G_NOARGS) ;
That is fine as far as it goes. The thing is, the Perl subroutine
can be specified as only a string. For Perl 4 this was adequate,
but Perl 5 allows references to subroutines and anonymous subroutines.
-This is where I<perl_call_sv> is useful.
+This is where I<call_sv> is useful.
The code below for I<CallSubSV> is identical to I<CallSubPV> except
that the C<name> parameter is now defined as an SV* and we use
-I<perl_call_sv> instead of I<perl_call_pv>.
+I<call_sv> instead of I<call_pv>.
void
CallSubSV(name)
SV * name
CODE:
PUSHMARK(SP) ;
- perl_call_sv(name, G_DISCARD|G_NOARGS) ;
+ call_sv(name, G_DISCARD|G_NOARGS) ;
Because we are using an SV to call I<fred> the following can all be used
@@ -1121,7 +1121,7 @@
CallSubSV($ref) ;
CallSubSV( sub { print "Hello there\n" } ) ;
-As you can see, I<perl_call_sv> gives you much greater flexibility in
+As you can see, I<call_sv> gives you much greater flexibility in
how you can specify the Perl subroutine.
You should note that if it is necessary to store the SV (C<name> in the
@@ -1141,7 +1141,7 @@
CallSavedSub1()
CODE:
PUSHMARK(SP) ;
- perl_call_sv(rememberSub, G_DISCARD|G_NOARGS) ;
+ call_sv(rememberSub, G_DISCARD|G_NOARGS) ;
The reason this is wrong is that by the time you come to use the
pointer C<rememberSub> in C<CallSavedSub1>, it may or may not still refer
@@ -1217,7 +1217,7 @@
CallSavedSub2()
CODE:
PUSHMARK(SP) ;
- perl_call_sv(keepSub, G_DISCARD|G_NOARGS) ;
+ call_sv(keepSub, G_DISCARD|G_NOARGS) ;
To avoid creating a new SV every time C<SaveSub2> is called,
the function first checks to see if it has been called before. If not,
@@ -1227,7 +1227,7 @@
the existing SV, C<keepSub>, is overwritten with the new value using
C<SvSetSV>.
-=head2 Using perl_call_argv
+=head2 Using call_argv
Here is a Perl subroutine which prints whatever parameters are passed
to it.
@@ -1239,7 +1239,7 @@
foreach (@list) { print "$_\n" }
}
-and here is an example of I<perl_call_argv> which will call
+and here is an example of I<call_argv> which will call
I<PrintList>.
static char * words[] = {"alpha", "beta", "gamma", "delta", NULL} ;
@@ -1249,13 +1249,13 @@
{
dSP ;
- perl_call_argv("PrintList", G_DISCARD, words) ;
+ call_argv("PrintList", G_DISCARD, words) ;
}
Note that it is not necessary to call C<PUSHMARK> in this instance.
-This is because I<perl_call_argv> will do it for you.
+This is because I<call_argv> will do it for you.
-=head2 Using perl_call_method
+=head2 Using call_method
Consider the following Perl code
@@ -1330,7 +1330,7 @@
XPUSHs(sv_2mortal(newSViv(index))) ;
PUTBACK;
- perl_call_method(method, G_DISCARD) ;
+ call_method(method, G_DISCARD) ;
void
call_PrintID(class, method)
@@ -1341,7 +1341,7 @@
XPUSHs(sv_2mortal(newSVpv(class, 0))) ;
PUTBACK;
- perl_call_method(method, G_DISCARD) ;
+ call_method(method, G_DISCARD) ;
So the methods C<PrintID> and C<Display> can be invoked like this
@@ -1352,7 +1352,7 @@
The only thing to note is that in both the static and virtual methods,
the method name is not passed via the stack--it is used as the first
-parameter to I<perl_call_method>.
+parameter to I<call_method>.
=head2 Using GIMME_V
@@ -1385,14 +1385,14 @@
=head2 Using Perl to dispose of temporaries
In the examples given to date, any temporaries created in the callback
-(i.e., parameters passed on the stack to the I<perl_call_*> function or
+(i.e., parameters passed on the stack to the I<call_*> function or
values returned via the stack) have been freed by one of these methods
=over 5
=item *
-specifying the G_DISCARD flag with I<perl_call_*>.
+specifying the G_DISCARD flag with I<call_*>.
=item *
@@ -1440,11 +1440,11 @@
...
error occurs
...
- external library --> perl_call --> perl
+ external library --> call_* --> perl
|
- perl <-- XSUB <-- external library <-- perl_call <----+
+ perl <-- XSUB <-- external library <-- call_* <----+
-After processing of the error using I<perl_call_*> is completed,
+After processing of the error using I<call_*> is completed,
control reverts back to Perl more or less immediately.
In the diagram, the further right you go the more deeply nested the
@@ -1457,22 +1457,22 @@
perl --> XSUB --> event handler
...
- event handler --> perl_call --> perl
+ event handler --> call_* --> perl
|
- event handler <-- perl_call <----+
+ event handler <-- call_* <----+
...
- event handler --> perl_call --> perl
+ event handler --> call_* --> perl
|
- event handler <-- perl_call <----+
+ event handler <-- call_* <----+
...
- event handler --> perl_call --> perl
+ event handler --> call_* --> perl
|
- event handler <-- perl_call <----+
+ event handler <-- call_* <----+
In this case the flow of control can consist of only the repeated
sequence
- event handler --> perl_call --> perl
+ event handler --> call_* --> perl
for practically the complete duration of the program. This means that
control may I<never> drop back to the surrounding scope in Perl at the
@@ -1532,7 +1532,7 @@
PUSHMARK(SP) ;
/* Call the Perl sub to process the callback */
- perl_call_sv(callback, G_DISCARD) ;
+ call_sv(callback, G_DISCARD) ;
}
@@ -1638,7 +1638,7 @@
PUTBACK ;
/* Call the Perl sub */
- perl_call_sv(*sv, G_DISCARD) ;
+ call_sv(*sv, G_DISCARD) ;
}
For completeness, here is C<asynch_close>. This shows how to remove
@@ -1721,7 +1721,7 @@
PUTBACK ;
/* Call the Perl sub */
- perl_call_sv(Map[index].PerlSub, G_DISCARD) ;
+ call_sv(Map[index].PerlSub, G_DISCARD) ;
}
static void
@@ -1875,7 +1875,7 @@
XPUSHs(sv_2mortal(newSViv(b)));
PUTBACK ;
- count = perl_call_pv("AddSubtract", G_ARRAY);
+ count = call_pv("AddSubtract", G_ARRAY);
SPAGAIN ;
SP -= count ;
@@ -1924,22 +1924,22 @@
=head2 Creating and calling an anonymous subroutine in C
-As we've already shown, C<perl_call_sv> can be used to invoke an
+As we've already shown, C<call_sv> can be used to invoke an
anonymous subroutine. However, our example showed a Perl script
invoking an XSUB to perform this operation. Let's see how it can be
done inside our C code:
...
- SV *cvrv = perl_eval_pv("sub { print 'You will not find me cluttering any namespace!' }", TRUE);
+ SV *cvrv = eval_pv("sub { print 'You will not find me cluttering any namespace!' }", TRUE);
...
- perl_call_sv(cvrv, G_VOID|G_NOARGS);
+ call_sv(cvrv, G_VOID|G_NOARGS);
-C<perl_eval_pv> is used to compile the anonymous subroutine, which
-will be the return value as well (read more about C<perl_eval_pv> in
-L<perlguts/perl_eval_pv>). Once this code reference is in hand, it
+C<eval_pv> is used to compile the anonymous subroutine, which
+will be the return value as well (read more about C<eval_pv> in
+L<perlguts/eval_pv>). Once this code reference is in hand, it
can be mixed in with all the previous examples we've shown.
=head1 SEE ALSO
==== //depot/perl/pod/perldiag.pod#128 (text) ====
Index: perl/pod/perldiag.pod
--- perl/pod/perldiag.pod.~1~ Tue Feb 29 14:29:41 2000
+++ perl/pod/perldiag.pod Tue Feb 29 14:29:41 2000
@@ -576,7 +576,7 @@
=item Callback called exit
-(F) A subroutine invoked from an external package via perl_call_sv()
+(F) A subroutine invoked from an external package via call_sv()
exited by calling exit.
=item Can't "goto" out of a pseudo block
==== //depot/perl/pod/perlembed.pod#20 (text) ====
Index: perl/pod/perlembed.pod
--- perl/pod/perlembed.pod.~1~ Tue Feb 29 14:29:41 2000
+++ perl/pod/perlembed.pod Tue Feb 29 14:29:41 2000
@@ -12,7 +12,7 @@
=item B<Use C from Perl?>
-Read L<perlxstut>, L<perlxs>, L<h2xs>, and L<perlguts>.
+Read L<perlxstut>, L<perlxs>, L<h2xs>, L<perlguts>, and L<perlapi>.
=item B<Use a Unix program from Perl?>
@@ -200,9 +200,9 @@
=head2 Calling a Perl subroutine from your C program
-To call individual Perl subroutines, you can use any of the B<perl_call_*>
+To call individual Perl subroutines, you can use any of the B<call_*>
functions documented in L<perlcall>.
-In this example we'll use C<perl_call_argv>.
+In this example we'll use C<call_argv>.
That's shown below, in a program I'll call I<showtime.c>.
@@ -221,7 +221,7 @@
/*** skipping perl_run() ***/
- perl_call_argv("showtime", G_DISCARD | G_NOARGS, args);
+ call_argv("showtime", G_DISCARD | G_NOARGS, args);
perl_destruct(my_perl);
perl_free(my_perl);
@@ -257,7 +257,7 @@
If you want to pass arguments to the Perl subroutine, you can add
strings to the C<NULL>-terminated C<args> list passed to
-I<perl_call_argv>. For other data types, or to examine return values,
+I<call_argv>. For other data types, or to examine return values,
you'll need to manipulate the Perl stack. That's demonstrated in the
last section of this document: L<Fiddling with the Perl stack from
your C program>.
@@ -265,7 +265,7 @@
=head2 Evaluating a Perl statement from your C program
Perl provides two API functions to evaluate pieces of Perl code.
-These are L<perlguts/perl_eval_sv> and L<perlguts/perl_eval_pv>.
+These are L<perlapi/eval_sv> and L<perlapi/eval_pv>.
Arguably, these are the only routines you'll ever need to execute
snippets of Perl code from within your C program. Your code can be as
@@ -273,7 +273,7 @@
L<perlfunc/use>, L<perlfunc/require>, and L<perlfunc/do> to
include external Perl files.
-I<perl_eval_pv> lets us evaluate individual Perl strings, and then
+I<eval_pv> lets us evaluate individual Perl strings, and then
extract variables for coercion into C types. The following program,
I<string.c>, executes three Perl strings, extracting an C<int> from
the first, a C<float> from the second, and a C<char *> from the third.
@@ -295,22 +295,22 @@
perl_run(my_perl);
/** Treat $a as an integer **/
- perl_eval_pv("$a = 3; $a **= 2", TRUE);
- printf("a = %d\n", SvIV(perl_get_sv("a", FALSE)));
+ eval_pv("$a = 3; $a **= 2", TRUE);
+ printf("a = %d\n", SvIV(get_sv("a", FALSE)));
/** Treat $a as a float **/
- perl_eval_pv("$a = 3.14; $a **= 2", TRUE);
- printf("a = %f\n", SvNV(perl_get_sv("a", FALSE)));
+ eval_pv("$a = 3.14; $a **= 2", TRUE);
+ printf("a = %f\n", SvNV(get_sv("a", FALSE)));
/** Treat $a as a string **/
- perl_eval_pv("$a = 'rekcaH lreP rehtonA tsuJ'; $a = reverse($a);", TRUE);
- printf("a = %s\n", SvPV(perl_get_sv("a", FALSE), n_a));
+ eval_pv("$a = 'rekcaH lreP rehtonA tsuJ'; $a = reverse($a);", TRUE);
+ printf("a = %s\n", SvPV(get_sv("a", FALSE), n_a));
perl_destruct(my_perl);
perl_free(my_perl);
}
-All of those strange functions with I<sv> in their names help convert Perl scalars to C types. They're described in L<perlguts>.
+All of those strange functions with I<sv> in their names help convert Perl scalars to C types. They're described in L<perlguts> and L<perlapi>.
If you compile and run I<string.c>, you'll see the results of using
I<SvIV()> to create an C<int>, I<SvNV()> to create a C<float>, and
@@ -323,11 +323,11 @@
In the example above, we've created a global variable to temporarily
store the computed value of our eval'd expression. It is also
possible and in most cases a better strategy to fetch the return value
-from I<perl_eval_pv()> instead. Example:
+from I<eval_pv()> instead. Example:
...
STRLEN n_a;
- SV *val = perl_eval_pv("reverse 'rekcaH lreP rehtonA tsuJ'", TRUE);
+ SV *val = eval_pv("reverse 'rekcaH lreP rehtonA tsuJ'", TRUE);
printf("%s\n", SvPV(val,n_a));
...
@@ -336,7 +336,7 @@
=head2 Performing Perl pattern matches and substitutions from your C program
-The I<perl_eval_sv()> function lets us evaluate strings of Perl code, so we can
+The I<eval_sv()> function lets us evaluate strings of Perl code, so we can
define some functions that use it to "specialize" in matches and
substitutions: I<match()>, I<substitute()>, and I<matches()>.
@@ -365,18 +365,18 @@
#include <EXTERN.h>
#include <perl.h>
- /** my_perl_eval_sv(code, error_check)
- ** kinda like perl_eval_sv(),
+ /** my_eval_sv(code, error_check)
+ ** kinda like eval_sv(),
** but we pop the return value off the stack
**/
- SV* my_perl_eval_sv(SV *sv, I32 croak_on_error)
+ SV* my_eval_sv(SV *sv, I32 croak_on_error)
{
dSP;
SV* retval;
STRLEN n_a;
PUSHMARK(SP);
- perl_eval_sv(sv, G_SCALAR);
+ eval_sv(sv, G_SCALAR);
SPAGAIN;
retval = POPs;
@@ -403,7 +403,7 @@
sv_setpvf(command, "my $string = '%s'; $string =~ %s",
SvPV(string,n_a), pattern);
- retval = my_perl_eval_sv(command, TRUE);
+ retval = my_eval_sv(command, TRUE);
SvREFCNT_dec(command);
return SvIV(retval);
@@ -425,10 +425,10 @@
sv_setpvf(command, "$string = '%s'; ($string =~ %s)",
SvPV(*string,n_a), pattern);
- retval = my_perl_eval_sv(command, TRUE);
+ retval = my_eval_sv(command, TRUE);
SvREFCNT_dec(command);
- *string = perl_get_sv("string", FALSE);
+ *string = get_sv("string", FALSE);
return SvIV(retval);
}
@@ -449,10 +449,10 @@
sv_setpvf(command, "my $string = '%s'; @array = ($string =~ %s)",
SvPV(string,n_a), pattern);
- my_perl_eval_sv(command, TRUE);
+ my_eval_sv(command, TRUE);
SvREFCNT_dec(command);
- *match_list = perl_get_av("array", FALSE);
+ *match_list = get_av("array", FALSE);
num_matches = av_len(*match_list) + 1; /** assume $[ is 0 **/
return num_matches;
@@ -539,7 +539,7 @@
First you'll need to know how to convert between C types and Perl
types, with newSViv() and sv_setnv() and newAV() and all their
-friends. They're described in L<perlguts>.
+friends. They're described in L<perlguts> and L<perlapi>.
Then you'll need to know how to manipulate the Perl stack. That's
described in L<perlcall>.
@@ -576,7 +576,7 @@
XPUSHs(sv_2mortal(newSViv(a))); /* push the base onto the stack */
XPUSHs(sv_2mortal(newSViv(b))); /* push the exponent onto stack */
PUTBACK; /* make local stack pointer global */
- perl_call_pv("expo", G_SCALAR); /* call the function */
+ call_pv("expo", G_SCALAR); /* call the function */
SPAGAIN; /* refresh stack pointer */
/* pop the return value from stack */
printf ("%d to the %dth power is %d.\n", a, b, POPi);
@@ -638,7 +638,7 @@
the code into that package using L<perlfunc/eval>. In the example
below, each file will only be compiled once. Or, the application
might choose to clean out the symbol table associated with the file
-after it's no longer needed. Using L<perlcall/perl_call_argv>, We'll
+after it's no longer needed. Using L<perlapi/call_argv>, We'll
call the subroutine C<Embed::Persistent::eval_file> which lives in the
file C<persistent.pl> and pass the filename and boolean cleanup/cache
flag as arguments.
@@ -750,7 +750,7 @@
/* call the subroutine, passing it the filename as an argument */
args[0] = filename;
- perl_call_argv("Embed::Persistent::eval_file",
+ call_argv("Embed::Persistent::eval_file",
G_DISCARD | G_EVAL, args);
/* check $@ */
@@ -953,7 +953,7 @@
% cc -c interp.c `perl -MExtUtils::Embed -e ccopts`
% cc -o interp perlxsi.o interp.o `perl -MExtUtils::Embed -e ldopts`
-Consult L<perlxs> and L<perlguts> for more details.
+Consult L<perlxs>, L<perlguts>, and L<perlapi> for more details.
=head1 Embedding Perl under Win32
==== //depot/perl/pod/perlguts.pod#53 (text) ====
Index: perl/pod/perlguts.pod
--- perl/pod/perlguts.pod.~1~ Tue Feb 29 14:29:41 2000
+++ perl/pod/perlguts.pod Tue Feb 29 14:29:41 2000
@@ -176,7 +176,7 @@
If you know the name of a scalar variable, you can get a pointer to its SV
by using the following:
- SV* perl_get_sv("package::varname", FALSE);
+ SV* get_sv("package::varname", FALSE);
This returns NULL if the variable does not exist.
@@ -287,7 +287,7 @@
If you know the name of an array variable, you can get a pointer to its AV
by using the following:
- AV* perl_get_av("package::varname", FALSE);
+ AV* get_av("package::varname", FALSE);
This returns NULL if the variable does not exist.
@@ -362,7 +362,7 @@
If you know the name of a hash variable, you can get a pointer to its HV
by using the following:
- HV* perl_get_hv("package::varname", FALSE);
+ HV* get_hv("package::varname", FALSE);
This returns NULL if the variable does not exist.
@@ -535,9 +535,9 @@
To create a new Perl variable with an undef value which can be accessed from
your Perl script, use the following routines, depending on the variable type.
- SV* perl_get_sv("package::varname", TRUE);
- AV* perl_get_av("package::varname", TRUE);
- HV* perl_get_hv("package::varname", TRUE);
+ SV* get_sv("package::varname", TRUE);
+ AV* get_av("package::varname", TRUE);
+ HV* get_hv("package::varname", TRUE);
Notice the use of TRUE as the second parameter. The new variable can now
be set, using the routines appropriate to the data type.
@@ -710,7 +710,7 @@
extern int dberror;
extern char *dberror_list;
- SV* sv = perl_get_sv("dberror", TRUE);
+ SV* sv = get_sv("dberror", TRUE);
sv_setiv(sv, (IV) dberror);
sv_setpv(sv, dberror_list[dberror]);
SvIOK_on(sv);
End of Patch.