From 39a14fad02382ad7256334689a46a1f17b6f766f Mon Sep 17 00:00:00 2001
From: Jan Dubois <jand@activestate.com>
Date: Wed, 24 May 2006 09:35:14 -0700
Subject: [PATCH] RE: perlhack.pod confused about POPSTACK From:  "Jan Dubois"
 <jand@activestate.com> Message-Id:  <03ee01c67f8a$b4d6aca0$2217a8c0@candy>

clean up davem's doc thinko of change #28292
p4raw-link: @28292 on //depot/perl: ed233832c7fe4d71f1f536650d0566b2e87ea46c

p4raw-id: //depot/perl@28303
---
 pod/perlhack.pod | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index df76d0f..fc3c686 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -1355,7 +1355,6 @@ roughly how the tied C<push> is implemented; see C<av_push> in F<av.c>:
      6	ENTER;
      7	call_method("PUSH", G_SCALAR|G_DISCARD);
      8	LEAVE;
-     9	(void)POPMARK;
 
 The lines which concern the mark stack are the first, fifth and last
 lines: they save away, restore and remove the current position of the
@@ -1397,11 +1396,6 @@ Perl space: C<call_method> takes care of that, and it's described in
 L<perlcall>. We call the C<PUSH> method in scalar context, and we're
 going to discard its return value.
 
-     9	(void)POPMARK;
-
-Finally, we remove the value we placed on the mark stack, since we
-don't need it any more.
-
 =item Save stack
 
 C doesn't have a concept of local scope, so perl provides one. We've
-- 
1.8.3.1