From 848805551b0f28dd093c1130af7aa30922a60349 Mon Sep 17 00:00:00 2001 From: Peter Scott Date: Thu, 24 Jan 2002 00:51:34 -0800 Subject: [PATCH] perldebguts.pod [bleadperl] Message-Id: <4.3.2.7.2.20020123073917.00bac740@mail.webquarry.com> p4raw-id: //depot/perl@14408 --- pod/perldebguts.pod | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod index 827bb2f..c46dfd9 100644 --- a/pod/perldebguts.pod +++ b/pod/perldebguts.pod @@ -19,8 +19,8 @@ F podpage in the Perl source tree. For example, whenever you call Perl's built-in C function from the package DB, the arguments that the corresponding stack -frame was called with are copied to the @DB::args array. The -general mechanisms is enabled by calling Perl with the B<-d> switch, the +frame was called with are copied to the C<@DB::args> array. The +general mechanism is enabled by calling Perl with the B<-d> switch, the following additional features are enabled (cf. L): =over 4 @@ -111,11 +111,12 @@ The minimal working debugger consists of one line sub DB::DB {} -which is quite handy as contents of C environment +which you could even fit into the C environment variable: $ PERL5DB="sub DB::DB {}" perl -d your-script +although it doesn't do anything that tells you it's working... Another brief debugger, slightly more useful, could be created with only the line: -- 2.7.4