summaryrefslogtreecommitdiff
path: root/av.c
diff options
context:
space:
mode:
authorDavid Mitchell <davem@iabyn.com>2015-10-06 11:50:06 +0100
committerDavid Mitchell <davem@iabyn.com>2015-10-20 16:51:48 +0100
commita4395ebabc865511588235b5953dce6cc458ed3c (patch)
tree8008e42c2f2a41dd1a5ca594271ab8a75666fc56 /av.c
parentc0755d0f10aaf12573eabf0bd12a4aa182802211 (diff)
downloadperl-a4395ebabc865511588235b5953dce6cc458ed3c.tar.gz
Improve pod for [ah]v_(clear|undef)
See [perl #117341].
Diffstat (limited to 'av.c')
-rw-r--r--av.c22
1 files changed, 15 insertions, 7 deletions
diff --git a/av.c b/av.c
index 2c4740b621..9a5644a0e2 100644
--- a/av.c
+++ b/av.c
@@ -436,11 +436,15 @@ Perl_av_make(pTHX_ SSize_t size, SV **strp)
/*
=for apidoc av_clear
-Clears an array, making it empty. Does not free the memory C<av> uses to
-store its list of scalars. If any destructors are triggered as a result,
-C<av> itself may be freed when this function returns.
+Frees the all the elements of an array, leaving it empty.
+The XS equivalent of C<@array = ()>. See also L</av_undef>.
-Perl equivalent: C<@myarray = ();>.
+Note that it is possible that the actions of a destructor called directly
+or indirectly by freeing an element of the array could cause the reference
+count of the array itself to be reduced (e.g. by deleting an entry in the
+symbol table). So it is a possibility that the AV could have been freed
+(or even reallocated) on return from the call unless you hold a reference
+to it.
=cut
*/
@@ -500,9 +504,13 @@ Perl_av_clear(pTHX_ AV *av)
/*
=for apidoc av_undef
-Undefines the array. Frees the memory used by the av to store its list of
-scalars. If any destructors are triggered as a result, C<av> itself may
-be freed.
+Undefines the array. The XS equivalent of C<undef(@array)>.
+
+As well as freeing all the elements of the array (like C<av_clear()>), this
+also frees the memory used by the av to store its list of scalars.
+
+See L</av_clear> for a note about the array possibly being invalid on
+return.
=cut
*/