From: Vincent Pit Date: Sat, 23 Feb 2008 12:04:43 +0000 (+0100) Subject: Re: [PATCH] POD fixes X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=0a3a8dc0cd7227e83cd26fe236d1ad57c4add668;p=p5sagit%2Fp5-mst-13.2.git Re: [PATCH] POD fixes Message-ID: <47BFFDCB.60107@profvince.com> p4raw-id: //depot/perl@33366 --- diff --git a/pod/perlreapi.pod b/pod/perlreapi.pod index f8e9984..b0d6275 100644 --- a/pod/perlreapi.pod +++ b/pod/perlreapi.pod @@ -334,7 +334,7 @@ just die when assigned to in the default engine. Get the C of a capture variable. There's a special callback for this so that perl doesn't have to do a FETCH and run C on the result, since the length is (in perl's case) known from an offset -stored in C<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; diff --git a/pod/perlreguts.pod b/pod/perlreguts.pod index 125a9f9..2049931 100644 --- a/pod/perlreguts.pod +++ b/pod/perlreguts.pod @@ -385,7 +385,7 @@ A grammar form might be something like this: =head3 Debug Output -In the 5.9.x development version of perl you can C< '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. diff --git a/pod/perlxs.pod b/pod/perlxs.pod index c045564..f88565b 100644 --- a/pod/perlxs.pod +++ b/pod/perlxs.pod @@ -2007,7 +2007,7 @@ comma, i.e. C<_aMY_CXT>, C, C<_pMY_CXT> and C. =item MY_CXT_CLONE By default, when a new interpreter is created as a copy of an existing one -(eg via C<create()>>), both interpreters share the same physical +(eg via C<< threads->create() >>), both interpreters share the same physical my_cxt_t structure. Calling C (typically via the package's C 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.