From 6e2bfd7f4281bd19f5eefda1f130d62ef05c8ead Mon Sep 17 00:00:00 2001
From: Gurusamy Sarathy <gsar@engin.umich.edu>
Date: Sat, 17 May 1997 20:59:27 +1200
Subject: perlguts caveats

Subject: Re: perlguts additions

On Sat, 17 May 1997 21:35:50 EDT, Spider Boardman wrote:
>Your first referenct to `mg_get', here:
>
>+a tied array, the caller will usually need to call C<mg_get(val)> to
>
>should be to `mg_set'.
>

Oops, thanks.

p5p-msgid: 199705180202.WAA22826@aatma.engin.umich.edu
Signed-off-by: Ilya Zakharevich <ilya@math.ohio-state.edu>
---
 pod/perlguts.pod | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'pod')

diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 33b51200cb..80f6d862a5 100644
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -836,7 +836,7 @@ The C<av_store> function, when given a tied array argument, merely
 copies the magic of the array onto the value to be "stored", using
 C<mg_copy>.  It may also return NULL, indicating that the value did not
 actually need to be stored in the array.  After a call to C<av_store> on
-a tied array, the caller will usually need to call C<mg_get(val)> to
+a tied array, the caller will usually need to call C<mg_set(val)> to
 actually invoke the perl level "STORE" method on the TIEARRAY object.  If
 C<av_store> did return NULL, a call to C<SvREFCNT_dec(val)> will also be
 usually necessary to avoid a memory leak.
-- 
cgit v1.2.1