In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/ffedb8cac4cef8f45c3d8879ddb708dc35dddd80?hp=28aafdbea124a4050118675c08f116781de5bd1d>
- Log ----------------------------------------------------------------- commit ffedb8cac4cef8f45c3d8879ddb708dc35dddd80 Author: Father Chrysostomos <[email protected]> Date: Sat Feb 12 09:38:29 2011 -0800 Bump re.pmâs version M ext/re/re.pm commit 57e8c15deb9ba396f62bf4832f676e7a853bd15e Author: Father Chrysostomos <[email protected]> Date: Sat Feb 12 09:36:18 2011 -0800 perldebug: capitalise titles The capitalisation was rather inconsistent throughout. M ext/re/re.pm M pod/perldebug.pod M pod/perlreref.pod commit d9f2b251b2a7966ba737c877bce9ffbe6120c836 Author: Father Chrysostomos <[email protected]> Date: Sat Feb 12 09:33:38 2011 -0800 Fix links to POD sections M pod/perldebug.pod M pod/perlretut.pod commit 7d0d50dd8561c325a5cc8339d10802fc08146961 Author: Father Chrysostomos <[email protected]> Date: Sat Feb 12 07:07:42 2011 -0800 perldebug: perl no longer includes the emacs mode M pod/perldebug.pod commit 5d464584654bdb70b228ec3a4222d0fbb4c1d469 Author: Father Chrysostomos <[email protected]> Date: Sat Feb 12 07:07:05 2011 -0800 perldebug tweaks M pod/perldebug.pod ----------------------------------------------------------------------- Summary of changes: ext/re/re.pm | 4 ++-- pod/perldebug.pod | 35 ++++++++++++++++++----------------- pod/perlreref.pod | 2 +- pod/perlretut.pod | 2 +- 4 files changed, 22 insertions(+), 21 deletions(-) diff --git a/ext/re/re.pm b/ext/re/re.pm index 100ef5b..850b948 100644 --- a/ext/re/re.pm +++ b/ext/re/re.pm @@ -4,7 +4,7 @@ package re; use strict; use warnings; -our $VERSION = "0.16"; +our $VERSION = "0.17"; our @ISA = qw(Exporter); our @EXPORT_OK = ('regmust', qw(is_regexp regexp_pattern @@ -323,7 +323,7 @@ form of output that can be used to get a colorful display on terminals that understand termcap color sequences. Set C<$ENV{PERL_RE_TC}> to a comma-separated list of C<termcap> properties to use for highlighting strings on/off, pre-point part on/off. -See L<perldebug/"Debugging regular expressions"> for additional info. +See L<perldebug/"Debugging Regular Expressions"> for additional info. As of 5.9.5 the directive C<use re 'debug'> and its equivalents are lexically scoped, as the other directives are. However they have both diff --git a/pod/perldebug.pod b/pod/perldebug.pod index 9e67b4d..07aa302 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -9,7 +9,7 @@ First of all, have you tried using the B<-w> switch? If you're new to the Perl debugger, you may prefer to read -L<perldebtut>, which is a tutorial introduction to the debugger . +L<perldebtut>, which is a tutorial introduction to the debugger. =head1 The Perl Debugger @@ -54,7 +54,7 @@ function with something that doesn't look like a debugger command, such as a leading C<;> or perhaps a C<+>, or by wrapping it with parentheses or braces. -=head2 Calling the debugger +=head2 Calling the Debugger There are several ways to call the debugger: @@ -388,7 +388,7 @@ Delete all watch-expressions. =item o X<debugger command, o> -Display all options +Display all options. =item o booloption ... X<debugger command, o> @@ -589,7 +589,7 @@ blessed object, or to a package name. =item M X<debugger command, M> -Displays all loaded modules and their versions +Display all loaded modules and their versions. =item man [manpage] @@ -876,7 +876,7 @@ corresponds to F</dev/ttyXX>, say, by issuing a command like See L<perldebguts/"Debugger Internals"> for details. -=head2 Debugger input/output +=head2 Debugger Input/Output =over 8 @@ -942,7 +942,7 @@ also from I<camel_flea>, but from line 4. If you execute the C<T> command from inside an active C<use> statement, the backtrace will contain both a C<require> frame and -an C<eval>) frame. +an C<eval> frame. =item Line Listing Format @@ -977,12 +977,12 @@ for incredibly long examples of these. =back -=head2 Debugging compile-time statements +=head2 Debugging Compile-Time Statements If you have compile-time executable statements (such as code within BEGIN, UNITCHECK and CHECK blocks or C<use> statements), these will I<not> be stopped by debugger, although C<require>s and INIT blocks -will, and compile-time statements can be traced with C<AutoTrace> +will, and compile-time statements can be traced with the C<AutoTrace> option set in C<PERLDB_OPTS>). From your own Perl code, however, you can transfer control back to the debugger using the following statement, which is harmless if the debugger is not running: @@ -1007,7 +1007,7 @@ compile subname> for the same purpose. The debugger probably contains enough configuration hooks that you won't ever have to modify it yourself. You may change the behaviour -of debugger from within the debugger using its C<o> command, from +of the debugger from within the debugger using its C<o> command, from the command line via the C<PERLDB_OPTS> environment variable, and from customization files. @@ -1056,13 +1056,13 @@ Note that any variables and functions that are not documented in this document (or in L<perldebguts>) are considered for internal use only, and as such are subject to change without notice. -=head2 Readline Support / History in the debugger +=head2 Readline Support / History in the Debugger As shipped, the only command-line history supplied is a simplistic one that checks for leading exclamation points. However, if you install the Term::ReadKey and Term::ReadLine modules from CPAN (such as Term::ReadLine::Gnu, Term::ReadLine::Perl, ...) you will -have full editing capabilities much like GNU I<readline>(3) provides. +have full editing capabilities much like those GNU I<readline>(3) provides. Look for these in the F<modules/by-module/Term> directory on CPAN. These do not support normal B<vi> command-line editing, however. @@ -1080,9 +1080,10 @@ it can interact with the Perl debugger to provide an integrated software development environment reminiscent of its interactions with C debuggers. -Perl comes with a start file for making B<emacs> act like a +Recent versions of Emacs come with a +start file for making B<emacs> act like a syntax-directed editor that understands (some of) Perl's syntax. -Look in the I<emacs> directory of the Perl source distribution. +See L<perlfaq3>. A similar setup by Tom Christiansen for interacting with any vendor-shipped B<vi> and the X11 window system is also available. @@ -1117,7 +1118,7 @@ interpret the information in that profile. More powerful profilers, such as C<Devel::NYTProf> are available from the CPAN: see L<perlperf> for details. -=head1 Debugging regular expressions +=head1 Debugging Regular Expressions X<regular expression, debugging> X<regex, debugging> X<regexp, debugging> @@ -1127,15 +1128,15 @@ voluminous output, one must not only have some idea about how regular expression matching works in general, but also know how Perl's regular expressions are internally compiled into an automaton. These matters are explored in some detail in -L<perldebguts/"Debugging regular expressions">. +L<perldebguts/"Debugging Regular Expressions">. -=head1 Debugging memory usage +=head1 Debugging Memory Usage X<memory usage> Perl contains internal support for reporting its own memory usage, but this is a fairly advanced concept that requires some understanding of how memory allocation works. -See L<perldebguts/"Debugging Perl memory usage"> for the details. +See L<perldebguts/"Debugging Perl Memory Usage"> for the details. =head1 SEE ALSO diff --git a/pod/perlreref.pod b/pod/perlreref.pod index 5247a63..54b619f 100644 --- a/pod/perlreref.pod +++ b/pod/perlreref.pod @@ -360,7 +360,7 @@ debugging. =item * -L<perldebug/"Debugging regular expressions"> +L<perldebug/"Debugging Regular Expressions"> =item * diff --git a/pod/perlretut.pod b/pod/perlretut.pod index e401bac..293683c 100644 --- a/pod/perlretut.pod +++ b/pod/perlretut.pod @@ -2838,7 +2838,7 @@ Each step is of the form S<C<< n <x> <y> >>>, with C<< <x> >> the part of the string matched and C<< <y> >> the part not yet matched. The S<C<< | 1: STAR >>> says that Perl is at line number 1 n the compilation list above. See -L<perldebguts/"Debugging regular expressions"> for much more detail. +L<perldebguts/"Debugging Regular Expressions"> for much more detail. An alternative method of debugging regexps is to embed C<print> statements within the regexp. This provides a blow-by-blow account of -- Perl5 Master Repository
