From: Rafael Garcia-Suarez Date: Wed, 17 Nov 2004 10:14:58 +0000 (+0000) Subject: Fix a couple of typos. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=4cdaeff7d67594a60bccc7882d3197ee0420932d;p=p5sagit%2Fp5-mst-13.2.git Fix a couple of typos. p4raw-id: //depot/perl@23508 --- diff --git a/hv.c b/hv.c index d3b86ed..2d04dda 100644 --- a/hv.c +++ b/hv.c @@ -1496,7 +1496,7 @@ Clears any placeholders from a hash. If a restricted hash has any of its keys marked as readonly and the key is subsequently deleted, the key is not actually deleted but is marked by assigning it a value of &PL_sv_placeholder. This tags it so it will be ignored by future operations such as iterating over the hash, -but will still allow the hash to have a value reaasigned to the key at some +but will still allow the hash to have a value reassigned to the key at some future point. This function clears any such placeholder keys from the hash. See Hash::Util::lock_keys() for an example of its use. diff --git a/utf8.c b/utf8.c index f12696e..7571e29 100644 --- a/utf8.c +++ b/utf8.c @@ -1928,7 +1928,7 @@ If the pe1 and pe2 are non-NULL, the scanning pointers will be copied in there (they will point at the beginning of the I character). If the pointers behind pe1 or pe2 are non-NULL, they are the end pointers beyond which scanning will not continue under any -circustances. If the byte lengths l1 and l2 are non-zero, s1+l1 and +circumstances. If the byte lengths l1 and l2 are non-zero, s1+l1 and s2+l2 will be used as goal end pointers that will also stop the scan, and which qualify towards defining a successful match: all the scans that define an explicit length must reach their goal pointers for