From: Stéphane Payrard <stef@mongueurs.net>
Date: Mon, 21 Jul 2003 21:36:59 +0000 (+0200)
Subject: [patch] perldebug.pod clarification
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=ea5ec3060d131488dc0c12046e95afc4ec64909a;p=p5sagit%2Fp5-mst-13.2.git

[patch] perldebug.pod clarification
Message-ID: <20030721193659.GC2722@stefp.dyndns.org>

p4raw-id: //depot/perl@20202
---

diff --git a/pod/perldebug.pod b/pod/perldebug.pod
index bde6701..ee9fa97 100644
--- a/pod/perldebug.pod
+++ b/pod/perldebug.pod
@@ -39,6 +39,12 @@ Any command not recognized by the debugger is directly executed
 (C<eval>'d) as Perl code in the current package.  (The debugger
 uses the DB package for keeping its own state information.)
 
+Note that the said C<eval> is bound by an implicit scope. As a
+result any newly introduced lexical variable or any modified
+capture buffer content is lost after the eval. The debugger is a
+nice environment to learn Perl, but if you interactively experiment using
+material which should be in the same scope, stuff it in one line.
+
 For any text entered at the debugger prompt, leading and trailing whitespace
 is first stripped before further processing.  If a debugger command
 coincides with some function in your own program, merely precede the