Change 33366 by [EMAIL PROTECTED] on 2008/02/25 08:10:14
Subject: Re: [PATCH] POD fixes
From: Vincent Pit <[EMAIL PROTECTED]>
Date: Sat, 23 Feb 2008 12:04:43 +0100
Message-ID: <[EMAIL PROTECTED]>
Affected files ...
... //depot/perl/pod/perlreapi.pod#15 edit
... //depot/perl/pod/perlreguts.pod#14 edit
... //depot/perl/pod/perlxs.pod#54 edit
Differences ...
==== //depot/perl/pod/perlreapi.pod#15 (text) ====
Index: perl/pod/perlreapi.pod
--- perl/pod/perlreapi.pod#14~32523~ 2007-11-27 07:04:18.000000000 -0800
+++ perl/pod/perlreapi.pod 2008-02-25 00:10:14.000000000 -0800
@@ -334,7 +334,7 @@
Get the C<length> of a capture variable. There's a special callback
for this so that perl doesn't have to do a FETCH and run C<length> on
the result, since the length is (in perl's case) known from an offset
-stored in C<<rx->offs> this is much more efficient:
+stored in C<< rx->offs >> this is much more efficient:
I32 s1 = rx->offs[paren].start;
I32 s2 = rx->offs[paren].end;
==== //depot/perl/pod/perlreguts.pod#14 (text) ====
Index: perl/pod/perlreguts.pod
--- perl/pod/perlreguts.pod#13~30922~ 2007-04-12 07:27:23.000000000 -0700
+++ perl/pod/perlreguts.pod 2008-02-25 00:10:14.000000000 -0800
@@ -385,7 +385,7 @@
=head3 Debug Output
-In the 5.9.x development version of perl you can C<<use re Debug => 'PARSE'>>
+In the 5.9.x development version of perl you can C<< use re Debug => 'PARSE' >>
to see some trace information about the parse process. We will start with some
simple patterns and build up to more complex patterns.
==== //depot/perl/pod/perlxs.pod#54 (text) ====
Index: perl/pod/perlxs.pod
--- perl/pod/perlxs.pod#53~32704~ 2007-12-22 09:00:24.000000000 -0800
+++ perl/pod/perlxs.pod 2008-02-25 00:10:14.000000000 -0800
@@ -2007,7 +2007,7 @@
=item MY_CXT_CLONE
By default, when a new interpreter is created as a copy of an existing one
-(eg via C<<threads->create()>>), both interpreters share the same physical
+(eg via C<< threads->create() >>), both interpreters share the same physical
my_cxt_t structure. Calling C<MY_CXT_CLONE> (typically via the package's
C<CLONE()> function), causes a byte-for-byte copy of the structure to be
taken, and any future dMY_CXT will cause the copy to be accessed instead.
End of Patch.
