perldelta(1)

1PERLDELTA(1)           Perl Programmers Reference Guide           PERLDELTA(1)
2
3
4

NAME

6       perldelta - what is new for perl v5.28.2
7

DESCRIPTION

9       This document describes differences between the 5.28.1 release and the
10       5.28.2 release.
11
12       If you are upgrading from an earlier release such as 5.28.0, first read
13       perl5281delta, which describes differences between 5.28.0 and 5.28.1.
14

Incompatible Changes

16   Any set of digits in the Common script are legal in a script run of another
17       script
18       There are several sets of digits in the Common script.  "[0-9]" is the
19       most familiar.  But there are also "[\x{FF10}-\x{FF19}]" (FULLWIDTH
20       DIGIT ZERO - FULLWIDTH DIGIT NINE), and several sets for use in
21       mathematical notation, such as the MATHEMATICAL DOUBLE-STRUCK DIGITs.
22       Any of these sets should be able to appear in script runs of, say,
23       Greek.  But the previous design overlooked all but the ASCII digits
24       "[0-9]", so the design was flawed.  This has been fixed, so is both a
25       bug fix and an incompatibility.
26
27       All digits in a run still have to come from the same set of ten digits.
28
29       [perl #133547] <https://rt.perl.org/Ticket/Display.html?id=133547>
30

Modules and Pragmata

32   Updated Modules and Pragmata
33       ·   Module::CoreList has been upgraded from version 5.20181129_28 to
34           5.20190419.
35
36       ·   PerlIO::scalar has been upgraded from version 0.29 to 0.30.
37
38       ·   Storable has been upgraded from version 3.08 to 3.08_01.
39

Platform Support

41   Platform-Specific Notes
42       Windows
43           The Windows Server 2003 SP1 Platform SDK build, with its early x64
44           compiler and tools, was accidentally broken in Perl 5.27.9.  This
45           has now been fixed.
46
47       Mac OS X
48           Perl's build and testing process on Mac OS X for "-Duseshrplib"
49           builds is now compatible with Mac OS X System Integrity Protection
50           (SIP).
51
52           SIP prevents binaries in /bin (and a few other places) being passed
53           the "DYLD_LIBRARY_PATH" environment variable.  For our purposes
54           this prevents "DYLD_LIBRARY_PATH" from being passed to the shell,
55           which prevents that variable being passed to the testing or build
56           process, so running "perl" couldn't find libperl.dylib.
57
58           To work around that, the initial build of the perl executable
59           expects to find libperl.dylib in the build directory, and the
60           library path is then adjusted during installation to point to the
61           installed library.
62
63           [perl #126706] <https://rt.perl.org/Ticket/Display.html?id=126706>
64

Selected Bug Fixes

66       ·   If an in-place edit is still in progress during global destruction
67           and the process exit code (as stored in $?) is zero, perl will now
68           treat the in-place edit as successful, replacing the input file
69           with any output produced.
70
71           This allows code like:
72
73             perl -i -ne 'print "Foo"; last'
74
75           to replace the input file, while code like:
76
77             perl -i -ne 'print "Foo"; die'
78
79           will not.  Partly resolves [perl #133659].
80
81           [perl #133659] <https://rt.perl.org/Ticket/Display.html?id=133659>
82
83       ·   A regression in Perl 5.28 caused the following code to fail
84
85            close(STDIN); open(CHILD, "|wc -l")'
86
87           because the child's stdin would be closed on exec.  This has now
88           been fixed.
89
90       ·   "pack "u", "invalid uuencoding"" now properly NUL terminates the
91           zero-length SV produced.
92
93           [perl #132655] <https://rt.perl.org/Ticket/Display.html?id=132655>
94
95       ·   Failing to compile a format now aborts compilation.  Like other
96           errors in sub-parses this could leave the parser in a strange
97           state, possibly crashing perl if compilation continued.
98
99           [perl #132158] <https://rt.perl.org/Ticket/Display.html?id=132158>
100
101       ·   See "Any set of digits in the Common script are legal in a script
102           run of another script".
103

Acknowledgements

105       Perl 5.28.2 represents approximately 4 months of development since Perl
106       5.28.1 and contains approximately 2,500 lines of changes across 75
107       files from 13 authors.
108
109       Excluding auto-generated files, documentation and release tools, there
110       were approximately 1,200 lines of changes to 29 .pm, .t, .c and .h
111       files.
112
113       Perl continues to flourish into its fourth decade thanks to a vibrant
114       community of users and developers.  The following people are known to
115       have contributed the improvements that became Perl 5.28.2:
116
117       Aaron Crane, Abigail, Andy Dougherty, David Mitchell, Karen Etheridge,
118       Karl Williamson, Leon Timmermans, Nicolas R., Sawyer X, Steve Hay, Tina
119       Mueller, Tony Cook, Zak B. Elep.
120
121       The list above is almost certainly incomplete as it is automatically
122       generated from version control history.  In particular, it does not
123       include the names of the (very much appreciated) contributors who
124       reported issues to the Perl bug tracker.
125
126       Many of the changes included in this version originated in the CPAN
127       modules included in Perl's core.  We're grateful to the entire CPAN
128       community for helping Perl to flourish.
129
130       For a more complete list of all of Perl's historical contributors,
131       please see the AUTHORS file in the Perl source distribution.
132

Reporting Bugs

134       If you find what you think is a bug, you might check the perl bug
135       database at <https://rt.perl.org/> .  There may also be information at
136       <http://www.perl.org/> , the Perl Home Page.
137
138       If you believe you have an unreported bug, please run the perlbug
139       program included with your release.  Be sure to trim your bug down to a
140       tiny but sufficient test case.  Your bug report, along with the output
141       of "perl -V", will be sent off to perlbug@perl.org to be analysed by
142       the Perl porting team.
143
144       If the bug you are reporting has security implications which make it
145       inappropriate to send to a publicly archived mailing list, then see
146       "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of
147       how to report the issue.
148

Give Thanks

150       If you wish to thank the Perl 5 Porters for the work we had done in
151       Perl 5, you can do so by running the "perlthanks" program:
152
153           perlthanks
154
155       This will send an email to the Perl 5 Porters list with your show of
156       thanks.
157