From a63ef1993d3cc3bed72e52e14345893e09a10a81 Mon Sep 17 00:00:00 2001 From: Shlomi Fish Date: Tue, 2 Jun 2015 11:53:03 +0300 Subject: [PATCH] Convert "\t" to spaces. \t looks differently depending on the tab width. This and two previous commits: For: RT #125310. --- pod/perlhacktips.pod | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pod/perlhacktips.pod b/pod/perlhacktips.pod index 06c8aa9..498a58d 100644 --- a/pod/perlhacktips.pod +++ b/pod/perlhacktips.pod @@ -79,7 +79,7 @@ If you want to have arrays of constant strings, note carefully the right combination of Cs: static const char * const yippee[] = - {"hi", "ho", "silver"}; + {"hi", "ho", "silver"}; There is a way to completely hide any modifiable globals (they are all moved to heap), the compilation setting @@ -1396,7 +1396,7 @@ variable PERL_DESTRUCT_LEVEL to a non-zero value. The t/TEST wrapper does set this to 2, and this is what you need to do too, if you don't want to see the "global leaks": For example, for running under valgrind - env PERL_DESTRUCT_LEVEL=2 valgrind ./perl -Ilib t/foo/bar.t + env PERL_DESTRUCT_LEVEL=2 valgrind ./perl -Ilib t/foo/bar.t (Note: the mod_perl apache module uses also this environment variable for its own purposes and extended its semantics. Refer to the mod_perl @@ -1443,10 +1443,10 @@ Unless C<-DPERL_MEM_LOG_NOIMPL> is also compiled, the logging functions read $ENV{PERL_MEM_LOG} to determine whether to log the event, and if so how: - $ENV{PERL_MEM_LOG} =~ /m/ Log all memory ops - $ENV{PERL_MEM_LOG} =~ /s/ Log all SV ops - $ENV{PERL_MEM_LOG} =~ /t/ include timestamp in Log - $ENV{PERL_MEM_LOG} =~ /^(\d+)/ write to FD given (default is 2) + $ENV{PERL_MEM_LOG} =~ /m/ Log all memory ops + $ENV{PERL_MEM_LOG} =~ /s/ Log all SV ops + $ENV{PERL_MEM_LOG} =~ /t/ include timestamp in Log + $ENV{PERL_MEM_LOG} =~ /^(\d+)/ write to FD given (default is 2) Memory logging is somewhat similar to C<-Dm> but is independent of C<-DDEBUGGING>, and at a higher level; all uses of Newx(), Renew(), and -- 1.8.3.1