New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
maybe small error in perlxs.pod example #9414
Comments
From ajrh@ajrh.netCreated by ajrh@ajrh.netIn the perlxs example (patched below), isn't the newmortal'd SV Inline Patch--- perlxs.pod.Orig 2008-07-12 13:14:11.000000000 -0400
+++ perlxs.pod 2008-07-12 13:16:16.974788521 -0400
@@ -1092,12 +1092,12 @@
char * host
PREINIT:
time_t timep;
bool_t x;
CODE:
- ST(0) = sv_newmortal();
if( rpcb_gettime( host, &timep ) ){
+ ST(0) = sv_newmortal();
sv_setnv( ST(0), (double)timep);
}
else{
ST(0) = &PL_sv_undef;
} Perl Info
|
From @mhxThe newmortal() SV isn't leaked. That's simply because it's "mortal", But you're right in that the example is suboptimal. The mortal SV Marcus |
The RT System itself - Status changed from 'new' to 'open' |
@mhx - Status changed from 'open' to 'resolved' |
From @mhxThe newmortal() SV isn't leaked. That's simply because it's "mortal", But you're right in that the example is suboptimal. The mortal SV Marcus |
From anthony@ajrh.netMarcus Holland-Moritz via RT wrote:
Are you sure? The mortal SV is no longer accessible via the stack
Well, that's fine then regardless. Thanks. Anthony |
From anthony@ajrh.netAnthony Heading wrote:
Ah - just read perlguts - I hadn't realized there was a separate A |
Migrated from rt.perl.org#56874 (status was 'resolved')
Searchable as RT56874$
The text was updated successfully, but these errors were encountered: