develooper Front page | perl.perl5.changes | Postings from October 2019

[perl.git] branch blead updated. v5.31.4-341-ge217699368

Max Maischein
October 11, 2019 11:25
[perl.git] branch blead updated. v5.31.4-341-ge217699368
Message ID:
In perl.git, the branch blead has been updated


- Log -----------------------------------------------------------------
commit e217699368be2cd45255ff5b86150be0463adb9c
Author: Max Maischein <>
Date:   Fri Oct 11 10:39:07 2019 +0200

    Move URLs to https:// in source code
    This URL is outdated, but the link forwards to the correct
    section in a PDF.


Summary of changes:
 perl.h         | 2 +-
 pod/perlre.pod | 8 ++++----
 regexec.c      | 4 ++--
 utf8.c         | 8 ++++----
 4 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/perl.h b/perl.h
index b1382e940d..13ab20a43f 100644
--- a/perl.h
+++ b/perl.h
@@ -7117,7 +7117,7 @@ extern void moncontrol(int);
 /* ISO 6429 NEL - C1 control NExt Line */
-/* See */
+/* See */
diff --git a/pod/perlre.pod b/pod/perlre.pod
index cc717075ac..9aab6730b5 100644
--- a/pod/perlre.pod
+++ b/pod/perlre.pod
@@ -667,7 +667,7 @@ characters.  The C<KELVIN SIGN>, for example matches the letters "k" and
 "K"; and C<LATIN SMALL LIGATURE FF> matches the sequence "ff", which,
 if you're not prepared, might make it look like a hexadecimal constant,
 presenting another potential security issue.  See
-L<> for a detailed discussion of Unicode
+L<> for a detailed discussion of Unicode
 security issues.
 This modifier may be specified to be the default by C<use feature
@@ -2594,7 +2594,7 @@ you can write either of these:
 In Taiwan, Japan, and Korea, it is common for text to have a mixture of
 characters from their native scripts and base Chinese.  Perl follows
-Unicode's UTS 39 (L<>) Unicode Security
+Unicode's UTS 39 (L<>) Unicode Security
 Mechanisms in allowing such mixtures.  For example, the Japanese scripts
 Katakana and Hiragana are commonly mixed together in practice, along
 with some Chinese characters, and hence are treated as being in a single
@@ -2642,7 +2642,7 @@ operation are subject to change; using it yields a warning in the
 C<experimental::script_run> category.
 The C<Script_Extensions> property as modified by UTS 39
-(L<>) is used as the basis for this
+(L<>) is used as the basis for this
 To summarize,
@@ -2677,7 +2677,7 @@ All characters in the sequence come from the Common script and/or the
 Inherited script and/or a single other script.
 The script of a character is determined by the C<Script_Extensions>
-property as modified by UTS 39 (L<>), as
+property as modified by UTS 39 (L<>), as
 described above.
 =item 3
diff --git a/regexec.c b/regexec.c
index 3c679c10ec..c80a3fa25a 100644
--- a/regexec.c
+++ b/regexec.c
@@ -4484,7 +4484,7 @@ STATIC bool
 S_isGCB(pTHX_ const GCB_enum before, const GCB_enum after, const U8 * const strbeg, const U8 * const curpos, const bool utf8_target)
     /* returns a boolean indicating if there is a Grapheme Cluster Boundary
-     * between the inputs.  See */
+     * between the inputs.  See */
@@ -4921,7 +4921,7 @@ S_isSB(pTHX_ SB_enum before,
              const bool utf8_target)
     /* returns a boolean indicating if there is a Sentence Boundary Break
-     * between the inputs.  See */
+     * between the inputs.  See */
     U8 * lpos = (U8 *) curpos;
     bool has_para_sep = FALSE;
diff --git a/utf8.c b/utf8.c
index bb4a858b01..3ead565fe6 100644
--- a/utf8.c
+++ b/utf8.c
@@ -486,7 +486,7 @@ Similarly, C<UNICODE_WARN_ILLEGAL_C9_INTERCHANGE> and
 C<UNICODE_DISALLOW_ILLEGAL_C9_INTERCHANGE> are shortcuts to select the
 above-Unicode and surrogate flags, but not the non-character ones, as
 defined in
-L<Unicode Corrigendum #9|>.
+L<Unicode Corrigendum #9|>.
 See L<perlunicode/Noncharacter code points>.
 Extremely high code points were never specified in any standard, and require an
@@ -1242,7 +1242,7 @@ disallow these categories individually.  C<UTF8_DISALLOW_ILLEGAL_INTERCHANGE>
 restricts the allowed inputs to the strict UTF-8 traditionally defined by
 Unicode.  Use C<UTF8_DISALLOW_ILLEGAL_C9_INTERCHANGE> to use the strictness
 definition given by
-L<Unicode Corrigendum #9|>.
+L<Unicode Corrigendum #9|>.
 The difference between traditional strictness and C9 strictness is that the
 latter does not forbid non-character code points.  (They are still discouraged,
 however.)  For more discussion see L<perlunicode/Noncharacter code points>.
@@ -1598,7 +1598,7 @@ Perl__utf8n_to_uvchr_msgs_helper(const U8 *s,
     /* The order of malformation tests here is important.  We should consume as
      * few bytes as possible in order to not skip any valid character.  This is
      * required by the Unicode Standard (section 3.9 of Unicode 6.0); see also
-     * for more discussion as to why.  For
+     * for more discussion as to why.  For
      * example, once we've done a UTF8SKIP, we can tell the expected number of
      * bytes, and could fail right off the bat if the input parameters indicate
      * that there are too few available.  But it could be that just that first
@@ -4941,7 +4941,7 @@ beyond what was matched.  Correspondingly for C<pe2> and C<s2>.
 For case-insensitiveness, the "casefolding" of Unicode is used
 instead of upper/lowercasing both the characters, see
-L<> (Case Mappings).
+L<> (Case Mappings).
 =cut */

Perl5 Master Repository Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About