diff options
| author | Karl Williamson <khw@cpan.org> | 2020-12-27 10:26:57 -0700 |
|---|---|---|
| committer | Karl Williamson <khw@cpan.org> | 2020-12-27 10:28:10 -0700 |
| commit | cbcd1db37b0359885fc7985026f88e9af3f368c3 (patch) | |
| tree | 56163b3323e1acf2e20f23a7364c216b984a0929 /sv.h | |
| parent | 1d440ec4903d5548d4d83f3e1d3547bbd528ae6f (diff) | |
| download | perl-cbcd1db37b0359885fc7985026f88e9af3f368c3.tar.gz | |
perlapi: Two references aren't yet links
This was causing a podcheck error
Diffstat (limited to 'sv.h')
| -rw-r--r-- | sv.h | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -1388,8 +1388,8 @@ object type. Exposed to perl code via Internals::SvREADONLY(). Low level micro optimization of C<L</SvGROW>>. It is generally better to use C<SvGROW> instead. This is because C<SvPV_renew> ignores potential issues that C<SvGROW> handles. C<sv> needs to have a real C<PV> that is unencombered by -things like COW. Using C<L</SV_CHECK_THINKFIRST>> or -C<L</SV_CHECK_THINKFIRST_COW_DROP>> before calling this should clean it up, but +things like COW. Using C<SV_CHECK_THINKFIRST> or +C<SV_CHECK_THINKFIRST_COW_DROP> before calling this should clean it up, but why not just use C<SvGROW> if you're not sure about the provenance? =cut |