At 2025-10-09T19:15:22-0500, G. Branden Robinson wrote: > Are the changes for the better or the worse? Let's see. I won't > scrutinize all 126, but just the first 13, assuming that's a random > enough sample (in other words, authors' punctuation and quotation > practices are not meaningfully correlated with the collation order of > the Debian packages that ship them [that's how dlocate(1) sorts its > output]).
It occurs to me that some people might want look over the other 113 cases. Diff attached. Regards, Branden
--- /tmp/pod-out-1.txt 2025-10-09 18:40:11.555940885 -0500
+++ /tmp/pod-out-2.txt 2025-10-09 18:45:03.518209913 -0500
@@ -9071,7 +9071,7 @@
ter behaved ‐‐ i.e., that they will be just like English.
But the Arabic translator is the next to write back. First off, your code
- for "I scanned %g directory." or "I scanned %g directories." assumes
+ for "I scanned %g directory." or "I scanned %g directories." assumes
there’s only singular or plural. But, to use linguistic jargon again, Ara‐
bic has grammatical number, like English (but unlike Chinese), but it’s a
three‐term category: singular, dual, and plural. In other words, the way
@@ -9692,7 +9692,7 @@
...emits the right text for this language. If the object in $lh belongs to
class "TkBocciBall::Localize::fr" and %TkBocciBall::Localize::fr::Lexicon
- contains "("You won!" => "Tu as gagne!")", then the above code happily
+ contains "("You won!" => "Tu as gagne!")", then the above code happily
tells the user "Tu as gagne!".
METHODS
@@ -16140,7 +16140,7 @@
(W regexp)(F) A character class range must start and end at a literal
character, not another character class like "\d" or "[:alpha:]". The
"-" in your false range is interpreted as a literal "-". In a
- "(?[...])" construct, this is an error, rather than a warning. Con‐
+ "(?[...])" construct, this is an error, rather than a warning. Con‐
sider quoting the "-", "\-". The <-- HERE shows whereabouts in the
regular expression the problem was discovered. See perlre.
@@ -18449,7 +18449,7 @@
ning with "[." and ending with ".]" is reserved for future extensions.
If you need to represent those character sequences inside a regular ex‐
pression character class, just quote the square brackets with the back‐
- slash: "\[." and ".\]". The <-- HERE shows whereabouts in the regular
+ slash: "\[." and ".\]". The <-- HERE shows whereabouts in the regular
expression the problem was discovered. See perlre.
POSIX syntax [= =] is reserved for future extensions in regex; marked by
@@ -36039,7 +36039,7 @@
time the event loop detects that the file descriptor given is readable
and/or writable).
- Each watcher type further has its own "ev_TYPE_set (watcher *, ...)" macro
+ Each watcher type further has its own "ev_TYPE_set (watcher *, ...)" macro
to configure it, with arguments specific to the watcher type. There is also
a macro to combine initialisation and setting in one call: "ev_TYPE_init
(watcher *, callback, ...)".
@@ -67681,7 +67681,7 @@
'command2' => [qw(sub1 sub2 sub3)]);
DESCRIPTION
- Creates "->commandSub(...)" as an alias for "->command('sub',...)" e.g.
+ Creates "->commandSub(...)" as an alias for "->command('sub',...)" e.g.
"->grabRelease" for "->grab('release')".
For each command/subcommand pair this creates a closure with command and
@@ -82112,7 +82112,7 @@
pragma.
The -T option is also forbidden on the "#!" line of a script, unless it was
- present on the Perl command line. Due to the way "#!" works, this usually
+ present on the Perl command line. Due to the way "#!" works, this usually
means that -T must be in the first argument. Thus:
#!/usr/bin/perl -T -w
@@ -90276,7 +90276,7 @@
Uppercase X/B allowed in hexadecimal/binary literals
Literals may now use either upper case "0X..." or "0B..." prefixes, in ad‐
- dition to the already supported "0x..." and "0b..." syntax [perl #76296].
+ dition to the already supported "0x..." and "0b..." syntax [perl #76296].
C, Ruby, Python, and PHP already support this syntax, and it makes Perl
more internally consistent: a round‐trip with "eval sprintf "%#X", 0x10"
@@ -90784,8 +90784,8 @@
On Windows parent processes would not terminate until all forked children
had terminated first. However, "kill("KILL", ...)" is inherently unstable
- on pseudo‐processes, and "kill("TERM", ...)" might not get delivered if
- the child is blocked in a system call.
+ on pseudo‐processes, and "kill("TERM", ...)" might not get delivered if the
+ child is blocked in a system call.
To avoid the deadlock and still provide a safe mechanism to terminate the
hosting process, Perl now no longer waits for children that have been sent
@@ -98278,7 +98278,7 @@
Splitting the tokens "(?" and "(*" in regular expressions
A deprecation warning is now raised if the "(" and "?" are separated by
white space or comments in "(?...)" regular expression constructs. Simi‐
- larly, if the "(" and "*" are separated in "(*VERB...)" constructs.
+ larly, if the "(" and "*" are separated in "(*VERB...)" constructs.
Pre‐PerlIO IO implementations
In theory, you can currently build perl without PerlIO. Instead, you’d use
@@ -106774,7 +106774,7 @@
the class is inverted or the sequence is specified as the beginning or
end of a range. In these cases, the only behavior change from before
is a slight rewording of the fatal error message given when this class
- is part of a "?[...])" construct. When the "[...]" stands alone, the
+ is part of a "?[...])" construct. When the "[...]" stands alone, the
same non‐fatal warning as before is raised, and only the first charac‐
ter in the sequence is used, again just as before.
@@ -107244,7 +107244,7 @@
a segfault instead of a proper error message. [perl #126180]
<https://rt.perl.org/Ticket/Display.html?id=126180>
- • Another problem with "(?[...])" constructs has been fixed wherein
+ • Another problem with "(?[...])" constructs has been fixed wherein
things like "\c]" could cause panics. [perl #126181]
<https://rt.perl.org/Ticket/Display.html?id=126181>
@@ -109220,7 +109220,7 @@
or a C-level assert. [perl #126615], [perl #126602], [perl #126193].
• There were places in regular expression patterns where comments
- ("(?#...)") weren’t allowed, but should have been. This is now fixed.
+ ("(?#...)") weren’t allowed, but should have been. This is now fixed.
[perl #116639] <https://rt.perl.org/Ticket/Display.html?id=116639>
• Some regressions from Perl 5.20 have been fixed, in which some syntax
@@ -109229,7 +109229,7 @@
#126180] <https://rt.perl.org/Ticket/Display.html?id=126180> [perl
#126404] <https://rt.perl.org/Ticket/Display.html?id=126404>
- • Another problem with "(?[...])" constructs has been fixed wherein
+ • Another problem with "(?[...])" constructs has been fixed wherein
things like "\c]" could cause panics. [perl #126181]
<https://rt.perl.org/Ticket/Display.html?id=126181>
@@ -113157,7 +113157,7 @@
been broken for many years.
Yada‐yada is now strictly a statement
- By the time of its initial stable release in Perl 5.12, the "..." (yada‐
+ By the time of its initial stable release in Perl 5.12, the "..." (yada‐
yada) operator was explicitly intended to serve as a statement, not an ex‐
pression. However, the original implementation was confused on this point,
leading to inconsistent parsing. The operator was accidentally accepted in
@@ -115652,7 +115652,7 @@
no longer produce spurious "Use of uninitialized value" warnings.
[perl #132683] <https://rt.perl.org/Ticket/Display.html?id=132683>.
- • Fix for "mutator not seen in (lex = ...) .= ..." [perl #133441]
+ • Fix for "mutator not seen in (lex = ...) .= ..." [perl #133441]
<https://rt.perl.org/Ticket/Display.html?id=133441>.
• "pack "u", "invalid uuencoding"" now properly NUL terminates the zero‐
@@ -117012,7 +117012,7 @@
• The "Code point 0x%X is not Unicode, and not portable" warning removed
the line "Code points above 0xFFFF_FFFF require larger than a 32 bit
- word." as code points that large are no longer legal on 32-bit plat‐
+ word." as code points that large are no longer legal on 32-bit plat‐
forms.
• Can’t use global %s in %s
@@ -118430,11 +118430,11 @@
constructors (open(), opendir(), pipe(), socketpair(), sysopen(), socket(),
and accept()) now autovivify a file or directory handle if the handle
passed to them is an uninitialized scalar variable. This allows the con‐
- structs such as "open(my $fh, ...)" and "open(local $fh,...)" to be used
- to create filehandles that will conveniently be closed automatically when
- the scope ends, provided there are no other references to them. This
- largely eliminates the need for typeglobs when opening filehandles that
- must be passed around, as in the following example:
+ structs such as "open(my $fh, ...)" and "open(local $fh,...)" to be used to
+ create filehandles that will conveniently be closed automatically when the
+ scope ends, provided there are no other references to them. This largely
+ eliminates the need for typeglobs when opening filehandles that must be
+ passed around, as in the following example:
sub myopen {
open my $fh, "@_"
@@ -121024,11 +121024,11 @@
constructors (open(), opendir(), pipe(), socketpair(), sysopen(), socket(),
and accept()) now autovivify a file or directory handle if the handle
passed to them is an uninitialized scalar variable. This allows the con‐
- structs such as "open(my $fh, ...)" and "open(local $fh,...)" to be used
- to create filehandles that will conveniently be closed automatically when
- the scope ends, provided there are no other references to them. This
- largely eliminates the need for typeglobs when opening filehandles that
- must be passed around, as in the following example:
+ structs such as "open(my $fh, ...)" and "open(local $fh,...)" to be used to
+ create filehandles that will conveniently be closed automatically when the
+ scope ends, provided there are no other references to them. This largely
+ eliminates the need for typeglobs when opening filehandles that must be
+ passed around, as in the following example:
sub myopen {
open my $fh, "@_"
@@ -124184,7 +124184,7 @@
"perlio" (which makes also the io/tell failure go away).
Perl 5.8.1 does build and work well with Cygwin 1.3: with (uname -a) "CYG‐
- WIN_NT-5.0 ... 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 ..." a 100% "make
+ WIN_NT-5.0 ... 1.3.22(0.78/3/2) 2003-03-18 09:20 i686 ..." a 100% "make
test" was achieved with "Configure -des -Duseithreads".
HP‐UX: HP cc warnings about sendfile and sendpath
@@ -126805,8 +126805,8 @@
perltoot provides information on modifying @UNIVERSAL::ISA.
- perlport documentation extended to include different "kill(-9, ...)" se‐
- mantics on Windows. It also clearly states "dump" is not supported on Win32
+ perlport documentation extended to include different "kill(-9, ...)" seman‐
+ tics on Windows. It also clearly states "dump" is not supported on Win32
and cygwin.
INSTALL has been updated and modernised.
@@ -150279,7 +150279,7 @@
File" above).
After the rc file is read, the debugger reads the $ENV{PERLDB_OPTS} envi‐
- ronment variable and parses this as the remainder of a "O ..." line as one
+ ronment variable and parses this as the remainder of a "O ..." line as one
might enter at the debugger prompt. You may place the initialization op‐
tions "TTY", "noTTY", "ReadLine", and "NonStop" there.
@@ -156798,7 +156798,7 @@
Raku is a reinvention of Perl, a language in the same lineage but not com‐
patible. The two are complementary, not mutually exclusive. Raku is not
- meant to replace Perl, and vice versa. See "What is Raku (Perl 6)?" below
+ meant to replace Perl, and vice versa. See "What is Raku (Perl 6)?" below
to find out more.
See perlhist for a history of Perl revisions.
@@ -166027,7 +166027,7 @@
task: "Filter::exec" and "Filter::sh". Both allow you to run any external
executable. Both use a coprocess to control the flow of data into and out
of the external executable. (For details on coprocesses, see Stephens,
- W.R., "Advanced Programming in the UNIX Environment." Addison‐Wesley, ISBN
+ W.R., "Advanced Programming in the UNIX Environment." Addison‐Wesley, ISBN
0-210-56317-7, pages 441-445.) The difference between them is that "Fil‐
ter::exec" spawns the external command directly, while "Filter::sh" spawns
a shell to execute the external command. (Unix uses the Bourne shell; NT
@@ -166521,7 +166521,7 @@
pseudo‐children have exited.
Starting with Perl 5.14 a parent will not wait() automatically for any
- child that has been signalled with "kill('TERM', ...)" to avoid a deadlock
+ child that has been signalled with "kill('TERM', ...)" to avoid a deadlock
in case the child is blocking on I/O and never receives the signal.
CAVEATS AND LIMITATIONS
@@ -188717,7 +188717,7 @@
v5.20, the distinctions between the platforms have mostly been made
invisible to most code, so this function is quite unlikely to be
what you want. If you do need this precise functionality, use in‐
- stead "NATIVE_TO_UNI(utf8_to_uvchr_buf(...))" or "NA‐
+ stead "NATIVE_TO_UNI(utf8_to_uvchr_buf(...))" or "NA‐
TIVE_TO_UNI(utf8n_to_uvchr(...))".
UV utf8n_to_uvuni(const U8 *s, STRLEN curlen,
@@ -212539,7 +212539,7 @@
=end html
- The command "=for formatname text..." specifies that the remainder of
+ The command "=for formatname text..." specifies that the remainder of
just this paragraph (starting right after formatname) is in that spe‐
cial format.
@@ -212769,7 +212769,7 @@
write ""NZ<><3"" (the "Z<>" breaks up the "N" and the "<" so they can’t
be considered the part of a (fictitious) "N<...>" code).
- Another use is to indicate that stuff in "=item Z<>stuff..." is not to
+ Another use is to indicate that stuff in "=item Z<>stuff..." is not to
be considered to be a bullet or number. For example, without the
"Z<>", the line
@@ -220431,8 +220431,8 @@
Another description starts with notions of "better"/"worse". All the sub‐
strings which may be matched by the given regular expression can be sorted
from the "best" match to the "worst" match, and it is the "best" match
- which is chosen. This substitutes the question of "what is chosen?" by
- the question of "which matches are better, and which are worse?".
+ which is chosen. This substitutes the question of "what is chosen?" by the
+ question of "which matches are better, and which are worse?".
Again, for elementary pieces there is no such question, since at most one
match at a given position is possible. This section describes the notion
@@ -227300,7 +227300,7 @@
# $2 = 'ming republic of Perl'
The first string position that this regexp can match is at the first 'm' in
- "programming". At this position, the minimal "m{1,2}?" matches just one
+ "programming". At this position, the minimal "m{1,2}?" matches just one
'm'. Although the second quantifier ".*?" would prefer to match no charac‐
ters, it is constrained by the end‐of‐string anchor '$' to match the rest
of the string.
@@ -227310,7 +227310,7 @@
# $2 = 'm'
# $3 = 'ming republic of Perl'
- In this regexp, you might expect the first minimal quantifier ".*?" to
+ In this regexp, you might expect the first minimal quantifier ".*?" to
match the empty string, because it is not constrained by a 'ˆ' anchor to
match the beginning of the word. Principle 0 applies here, however. Be‐
cause it is possible for the whole regexp to match at the start of the
@@ -239595,7 +239595,7 @@
dition)yes-pattern)", an integer in parentheses, a lookahead/look‐
behind/evaluate zero‐width assertion;, a name in angle brackets or
single quotes, the special symbol "(R)", "(1)" "(2)" .., "(<NAME>)"
- "('NAME')", "(?=...)" "(?!...)" "(?<=...)" "(?<!...)", "(?{ CODE
+ "('NAME')", "(?=...)" "(?!...)" "(?<=...)" "(?<!...)", "(?{ CODE
})", "(R)", "(R1)" "(R2)" .., "(R&NAME)", "(DEFINE)", "(?>pat‐
tern)", "(*atomic:pattern)"
@@ -284401,7 +284401,7 @@
|
Clause processing stopped here ------/
- It is also possible to invert a single rule by prefixing it with "!" like
+ It is also possible to invert a single rule by prefixing it with "!" like
so:
# large files that aren't videos
@@ -330207,7 +330207,7 @@
* I personally would update GitHub at the point I was reasonably confident
I could hack it, just to prevent myself from having to update GitHub again
- in a week or so saying "oops, bit off more than I could chew." But that’s
+ in a week or so saying "oops, bit off more than I could chew." But that’s
me talking.
* Development requires using Module::Build rather than ExtUtils::MakeMaker.
signature.asc
Description: PGP signature
