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
newPVOP documentation is misleading #15226
Comments
From @maukeCreated by @maukeperldoc perlapi: newPVOP Constructs, checks, and returns an op of any type that involves an OP * newPVOP(I32 type, I32 flags, char *pv) "the memory will be freed when the op is destroyed" is arguably wrong. The (I discovered this while trying to use newPVOP(OP_CUSTOM, 0, ptr).) Perl Info
|
From @iabynOn Sat, Mar 12, 2016 at 03:04:16PM -0800, l.mai@web.de wrote:
I suppose the question is whether to fix the code or the docs. Having had a quick look at op_clear(), I also note that there is a latent -- |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynOn Mon, Mar 14, 2016 at 09:33:54AM +0000, Dave Mitchell wrote:
I still don't know the answer to that.
I've fixed that now with v5.25.9-32-gabd07ec -- |
From zefram@fysh.orgDave Mitchell wrote:
The nature of op handling is such that the code is canonical, -zefram |
@xsawyerx - Status changed from 'open' to 'pending release' |
From @khwilliamsonThank you for filing this report. You have helped make Perl better. With the release yesterday of Perl 5.28.0, this and 185 other issues have been Perl 5.28.0 may be downloaded via: If you find that the problem persists, feel free to reopen this ticket. |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#127697 (status was 'resolved')
Searchable as RT127697$
The text was updated successfully, but these errors were encountered: