summaryrefslogtreecommitdiff
path: root/pod/perldebguts.pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2002-03-20 01:12:28 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2002-03-20 01:12:28 +0000
commit666f95b95a2f6347f7b7bbc8951144df2db05479 (patch)
tree6ea986aac1eb964fda56cdb50886230054002bd0 /pod/perldebguts.pod
parentb310b0538cc1a7948587a9e5ff30683fec2a3ece (diff)
downloadperl-666f95b95a2f6347f7b7bbc8951144df2db05479.tar.gz
Whitespace tweaks.
p4raw-id: //depot/perl@15351
Diffstat (limited to 'pod/perldebguts.pod')
-rw-r--r--pod/perldebguts.pod10
1 files changed, 5 insertions, 5 deletions
diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod
index f507ac8997..cde70b2fb0 100644
--- a/pod/perldebguts.pod
+++ b/pod/perldebguts.pod
@@ -111,15 +111,15 @@ calls are not possible, even though C<&DB::sub> exists.
=head2 Writing Your Own Debugger
=head3 Environment Variables
-
+
The C<PERL5DB> environment variable can be used to define a debugger.
For example, the minimal "working" debugger (it actually doesn't do anything)
consists of one line:
-
+
sub DB::DB {}
It can easily be defined like this:
-
+
$ PERL5DB="sub DB::DB {}" perl -d your-script
Another brief debugger, slightly more useful, can be created
@@ -130,9 +130,9 @@ with only the line:
This debugger prints a number which increments for each statement
encountered and waits for you to hit a newline before continuing
to the next statement.
-
+
The following debugger is actually useful:
-
+
{
package DB;
sub DB {}