summaryrefslogtreecommitdiffstats
path: root/upstream/mageia-cauldron/man1/perl5181delta.1
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/mageia-cauldron/man1/perl5181delta.1')
-rw-r--r--upstream/mageia-cauldron/man1/perl5181delta.1221
1 files changed, 221 insertions, 0 deletions
diff --git a/upstream/mageia-cauldron/man1/perl5181delta.1 b/upstream/mageia-cauldron/man1/perl5181delta.1
new file mode 100644
index 00000000..9e54b489
--- /dev/null
+++ b/upstream/mageia-cauldron/man1/perl5181delta.1
@@ -0,0 +1,221 @@
+.\" -*- mode: troff; coding: utf-8 -*-
+.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
+.\"
+.\" Standard preamble:
+.\" ========================================================================
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Vb \" Begin verbatim text
+.ft CW
+.nf
+.ne \\$1
+..
+.de Ve \" End verbatim text
+.ft R
+.fi
+..
+.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
+.ie n \{\
+. ds C` ""
+. ds C' ""
+'br\}
+.el\{\
+. ds C`
+. ds C'
+'br\}
+.\"
+.\" Escape single quotes in literal strings from groff's Unicode transform.
+.ie \n(.g .ds Aq \(aq
+.el .ds Aq '
+.\"
+.\" If the F register is >0, we'll generate index entries on stderr for
+.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
+.\" entries marked with X<> in POD. Of course, you'll have to process the
+.\" output yourself in some meaningful fashion.
+.\"
+.\" Avoid warning from groff about undefined register 'F'.
+.de IX
+..
+.nr rF 0
+.if \n(.g .if rF .nr rF 1
+.if (\n(rF:(\n(.g==0)) \{\
+. if \nF \{\
+. de IX
+. tm Index:\\$1\t\\n%\t"\\$2"
+..
+. if !\nF==2 \{\
+. nr % 0
+. nr F 2
+. \}
+. \}
+.\}
+.rr rF
+.\" ========================================================================
+.\"
+.IX Title "PERL5181DELTA 1"
+.TH PERL5181DELTA 1 2023-11-28 "perl v5.38.2" "Perl Programmers Reference Guide"
+.\" For nroff, turn off justification. Always turn off hyphenation; it makes
+.\" way too many mistakes in technical documents.
+.if n .ad l
+.nh
+.SH NAME
+perl5181delta \- what is new for perl v5.18.1
+.SH DESCRIPTION
+.IX Header "DESCRIPTION"
+This document describes differences between the 5.18.0 release and the 5.18.1
+release.
+.PP
+If you are upgrading from an earlier release such as 5.16.0, first read
+perl5180delta, which describes differences between 5.16.0 and 5.18.0.
+.SH "Incompatible Changes"
+.IX Header "Incompatible Changes"
+There are no changes intentionally incompatible with 5.18.0
+If any exist, they are bugs, and we request that you submit a
+report. See "Reporting Bugs" below.
+.SH "Modules and Pragmata"
+.IX Header "Modules and Pragmata"
+.SS "Updated Modules and Pragmata"
+.IX Subsection "Updated Modules and Pragmata"
+.IP \(bu 4
+B has been upgraded from 1.42 to 1.42_01, fixing bugs related to lexical
+subroutines.
+.IP \(bu 4
+Digest::SHA has been upgraded from 5.84 to 5.84_01, fixing a crashing bug.
+[RT #118649]
+.IP \(bu 4
+Module::CoreList has been upgraded from 2.89 to 2.96.
+.SH "Platform Support"
+.IX Header "Platform Support"
+.SS "Platform-Specific Notes"
+.IX Subsection "Platform-Specific Notes"
+.IP AIX 4
+.IX Item "AIX"
+A rarely-encountered configuration bug in the AIX hints file has been corrected.
+.IP MidnightBSD 4
+.IX Item "MidnightBSD"
+After a patch to the relevant hints file, perl should now build correctly on
+MidnightBSD 0.4\-RELEASE.
+.SH "Selected Bug Fixes"
+.IX Header "Selected Bug Fixes"
+.IP \(bu 4
+Starting in v5.18.0, a construct like \f(CW\*(C`/[#](?{})/x\*(C'\fR would have its \f(CW\*(C`#\*(C'\fR
+incorrectly interpreted as a comment. The code block would be skipped,
+unparsed. This has been corrected.
+.IP \(bu 4
+A number of memory leaks related to the new, experimental regexp bracketed
+character class feature have been plugged.
+.IP \(bu 4
+The OP allocation code now returns correctly aligned memory in all cases
+for \f(CW\*(C`struct pmop\*(C'\fR. Previously it could return memory only aligned to a
+4\-byte boundary, which is not correct for an ithreads build with 64 bit IVs
+on some 32 bit platforms. Notably, this caused the build to fail completely
+on sparc GNU/Linux. [RT #118055]
+.IP \(bu 4
+The debugger's \f(CW\*(C`man\*(C'\fR command been fixed. It was broken in the v5.18.0
+release. The \f(CW\*(C`man\*(C'\fR command is aliased to the names \f(CW\*(C`doc\*(C'\fR and \f(CW\*(C`perldoc\*(C'\fR \-
+all now work again.
+.IP \(bu 4
+\&\f(CW@_\fR is now correctly visible in the debugger, fixing a regression
+introduced in v5.18.0's debugger. [RT #118169]
+.IP \(bu 4
+Fixed a small number of regexp constructions that could either fail to
+match or crash perl when the string being matched against was
+allocated above the 2GB line on 32\-bit systems. [RT #118175]
+.IP \(bu 4
+Perl v5.16 inadvertently introduced a bug whereby calls to XSUBs that were
+not visible at compile time were treated as lvalues and could be assigned
+to, even when the subroutine was not an lvalue sub. This has been fixed.
+[perl #117947]
+.IP \(bu 4
+Perl v5.18 inadvertently introduced a bug whereby dual-vars (i.e.
+variables with both string and numeric values, such as \f(CW$!\fR ) where the
+truthness of the variable was determined by the numeric value rather than
+the string value. [RT #118159]
+.IP \(bu 4
+Perl v5.18 inadvertently introduced a bug whereby interpolating mixed up\-
+and down-graded UTF\-8 strings in a regex could result in malformed UTF\-8
+in the pattern: specifically if a downgraded character in the range
+\&\f(CW\*(C`\ex80..\exff\*(C'\fR followed a UTF\-8 string, e.g.
+.Sp
+.Vb 3
+\& utf8::upgrade( my $u = "\ex{e5}");
+\& utf8::downgrade(my $d = "\ex{e5}");
+\& /$u$d/
+.Ve
+.Sp
+[perl #118297].
+.IP \(bu 4
+Lexical constants (\f(CW\*(C`my sub a() { 42 }\*(C'\fR) no longer crash when inlined.
+.IP \(bu 4
+Parameter prototypes attached to lexical subroutines are now respected when
+compiling sub calls without parentheses. Previously, the prototypes were
+honoured only for calls \fIwith\fR parentheses. [RT #116735]
+.IP \(bu 4
+Syntax errors in lexical subroutines in combination with calls to the same
+subroutines no longer cause crashes at compile time.
+.IP \(bu 4
+The dtrace sub-entry probe now works with lexical subs, instead of
+crashing [perl #118305].
+.IP \(bu 4
+Undefining an inlinable lexical subroutine (\f(CWmy sub foo() { 42 } undef
+&foo\fR) would result in a crash if warnings were turned on.
+.IP \(bu 4
+Deep recursion warnings no longer crash lexical subroutines. [RT #118521]
+.SH Acknowledgements
+.IX Header "Acknowledgements"
+Perl 5.18.1 represents approximately 2 months of development since Perl 5.18.0
+and contains approximately 8,400 lines of changes across 60 files from 12
+authors.
+.PP
+Perl continues to flourish into its third decade thanks to a vibrant community
+of users and developers. The following people are known to have contributed the
+improvements that became Perl 5.18.1:
+.PP
+Chris 'BinGOs' Williams, Craig A. Berry, Dagfinn Ilmari Mannsåker, David
+Mitchell, Father Chrysostomos, Karl Williamson, Lukas Mai, Nicholas Clark,
+Peter Martini, Ricardo Signes, Shlomi Fish, Tony Cook.
+.PP
+The list above is almost certainly incomplete as it is automatically generated
+from version control history. In particular, it does not include the names of
+the (very much appreciated) contributors who reported issues to the Perl bug
+tracker.
+.PP
+Many of the changes included in this version originated in the CPAN modules
+included in Perl's core. We're grateful to the entire CPAN community for
+helping Perl to flourish.
+.PP
+For a more complete list of all of Perl's historical contributors, please see
+the \fIAUTHORS\fR file in the Perl source distribution.
+.SH "Reporting Bugs"
+.IX Header "Reporting Bugs"
+If you find what you think is a bug, you might check the articles recently
+posted to the comp.lang.perl.misc newsgroup and the perl bug database at
+http://rt.perl.org/perlbug/ . There may also be information at
+http://www.perl.org/ , the Perl Home Page.
+.PP
+If you believe you have an unreported bug, please run the perlbug program
+included with your release. Be sure to trim your bug down to a tiny but
+sufficient test case. Your bug report, along with the output of \f(CW\*(C`perl \-V\*(C'\fR,
+will be sent off to perlbug@perl.org to be analysed by the Perl porting team.
+.PP
+If the bug you are reporting has security implications, which make it
+inappropriate to send to a publicly archived mailing list, then please send it
+to perl5\-security\-report@perl.org. This points to a closed subscription
+unarchived mailing list, which includes all the core committers, who will be
+able to help assess the impact of issues, figure out a resolution, and help
+co-ordinate the release of patches to mitigate or fix the problem across all
+platforms on which Perl is supported. Please only use this address for
+security issues in the Perl core, not for modules independently distributed on
+CPAN.
+.SH "SEE ALSO"
+.IX Header "SEE ALSO"
+The \fIChanges\fR file for an explanation of how to view exhaustive details on
+what changed.
+.PP
+The \fIINSTALL\fR file for how to build Perl.
+.PP
+The \fIREADME\fR file for general stuff.
+.PP
+The \fIArtistic\fR and \fICopying\fR files for copyright information.