Debian Codegraph @

upstream/mageia-cauldron/man1/perl581delta.1

raw
1 .\" -*- mode: troff; coding: utf-8 -*-
2 .\" Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45)
3 .\"
4 .\" Standard preamble:
5 .\" ========================================================================
6 .de Sp \" Vertical space (when we can't use .PP)
7 .if t .sp .5v
8 .if n .sp
9 ..
10 .de Vb \" Begin verbatim text
11 .ft CW
12 .nf
13 .ne \\$1
14 ..
15 .de Ve \" End verbatim text
16 .ft R
17 .fi
18 ..
19 .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
20 .ie n \{\
21 . ds C` ""
22 . ds C' ""
23 'br\}
24 .el\{\
25 . ds C`
26 . ds C'
27 'br\}
28 .\"
29 .\" Escape single quotes in literal strings from groff's Unicode transform.
30 .ie \n(.g .ds Aq \(aq
31 .el .ds Aq '
32 .\"
33 .\" If the F register is >0, we'll generate index entries on stderr for
34 .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
35 .\" entries marked with X<> in POD. Of course, you'll have to process the
36 .\" output yourself in some meaningful fashion.
37 .\"
38 .\" Avoid warning from groff about undefined register 'F'.
39 .de IX
40 ..
41 .nr rF 0
42 .if \n(.g .if rF .nr rF 1
43 .if (\n(rF:(\n(.g==0)) \{\
44 . if \nF \{\
45 . de IX
46 . tm Index:\\$1\t\\n%\t"\\$2"
47 ..
48 . if !\nF==2 \{\
49 . nr % 0
50 . nr F 2
51 . \}
52 . \}
53 .\}
54 .rr rF
55 .\"
56 .\" Required to disable full justification in groff 1.23.0.
57 .if n .ds AD l
58 .\" ========================================================================
59 .\"
60 .IX Title "PERL581DELTA 1"
61 .TH PERL581DELTA 1 2025-06-24 "perl v5.42.0" "Perl Programmers Reference Guide"
62 .\" For nroff, turn off justification. Always turn off hyphenation; it makes
63 .\" way too many mistakes in technical documents.
64 .if n .ad l
65 .nh
66 .SH NAME
67 perl581delta \- what is new for perl v5.8.1
68 .SH DESCRIPTION
69 .IX Header "DESCRIPTION"
70 This document describes differences between the 5.8.0 release and
71 the 5.8.1 release.
72 .PP
73 If you are upgrading from an earlier release such as 5.6.1, first read
74 the perl58delta, which describes differences between 5.6.0 and
75 5.8.0.
76 .PP
77 In case you are wondering about 5.6.1, it was bug\-fix\-wise rather
78 identical to the development release 5.7.1. Confused? This timeline
79 hopefully helps a bit: it lists the new major releases, their maintenance
80 releases, and the development releases.
81 .PP
82 .Vb 1
83 \& New Maintenance Development
84 \&
85 \& 5.6.0 2000\-Mar\-22
86 \& 5.7.0 2000\-Sep\-02
87 \& 5.6.1 2001\-Apr\-08
88 \& 5.7.1 2001\-Apr\-09
89 \& 5.7.2 2001\-Jul\-13
90 \& 5.7.3 2002\-Mar\-05
91 \& 5.8.0 2002\-Jul\-18
92 \& 5.8.1 2003\-Sep\-25
93 .Ve
94 .SH "Incompatible Changes"
95 .IX Header "Incompatible Changes"
96 .SS "Hash Randomisation"
97 .IX Subsection "Hash Randomisation"
98 Mainly due to security reasons, the "random ordering" of hashes
99 has been made even more random. Previously while the order of hash
100 elements from \fBkeys()\fR, \fBvalues()\fR, and \fBeach()\fR was essentially random,
101 it was still repeatable. Now, however, the order varies between
102 different runs of Perl.
103 .PP
104 \&\fBPerl has never guaranteed any ordering of the hash keys\fR, and the
105 ordering has already changed several times during the lifetime of
106 Perl 5. Also, the ordering of hash keys has always been, and
107 continues to be, affected by the insertion order.
108 .PP
109 The added randomness may affect applications.
110 .PP
111 One possible scenario is when output of an application has included
112 hash data. For example, if you have used the Data::Dumper module to
113 dump data into different files, and then compared the files to see
114 whether the data has changed, now you will have false positives since
115 the order in which hashes are dumped will vary. In general the cure
116 is to sort the keys (or the values); in particular for Data::Dumper to
117 use the \f(CW\*(C`Sortkeys\*(C'\fR option. If some particular order is really
118 important, use tied hashes: for example the Tie::IxHash module
119 which by default preserves the order in which the hash elements
120 were added.
121 .PP
122 More subtle problem is reliance on the order of "global destruction".
123 That is what happens at the end of execution: Perl destroys all data
124 structures, including user data. If your destructors (the DESTROY
125 subroutines) have assumed any particular ordering to the global
126 destruction, there might be problems ahead. For example, in a
127 destructor of one object you cannot assume that objects of any other
128 class are still available, unless you hold a reference to them.
129 If the environment variable PERL_DESTRUCT_LEVEL is set to a non\-zero
130 value, or if Perl is exiting a spawned thread, it will also destruct
131 the ordinary references and the symbol tables that are no longer in use.
132 You can\*(Aqt call a class method or an ordinary function on a class that
133 has been collected that way.
134 .PP
135 The hash randomisation is certain to reveal hidden assumptions about
136 some particular ordering of hash elements, and outright bugs: it
137 revealed a few bugs in the Perl core and core modules.
138 .PP
139 To disable the hash randomisation in runtime, set the environment
140 variable PERL_HASH_SEED to 0 (zero) before running Perl (for more
141 information see "PERL_HASH_SEED" in perlrun), or to disable the feature
142 completely in compile time, compile with \f(CW\*(C`\-DNO_HASH_SEED\*(C'\fR (see \fIINSTALL\fR).
143 .PP
144 See "Algorithmic Complexity Attacks" in perlsec for the original
145 rationale behind this change.
146 .SS "UTF\-8 On Filehandles No Longer Activated By Locale"
147 .IX Subsection "UTF-8 On Filehandles No Longer Activated By Locale"
148 In Perl 5.8.0 all filehandles, including the standard filehandles,
149 were implicitly set to be in Unicode UTF\-8 if the locale settings
150 indicated the use of UTF\-8. This feature caused too many problems,
151 so the feature was turned off and redesigned: see "Core Enhancements".
152 .SS "Single\-number v\-strings are no longer v\-strings before ""=>"""
153 .IX Subsection "Single-number v-strings are no longer v-strings before ""=>"""
154 The version strings or v\-strings (see "Version Strings" in perldata)
155 feature introduced in Perl 5.6.0 has been a source of some confusion\-\-
156 especially when the user did not want to use it, but Perl thought it
157 knew better. Especially troublesome has been the feature that before
158 a "=>" a version string (a "v" followed by digits) has been interpreted
159 as a v\-string instead of a string literal. In other words:
160 .PP
161 .Vb 1
162 \& %h = ( v65 => 42 );
163 .Ve
164 .PP
165 has meant since Perl 5.6.0
166 .PP
167 .Vb 1
168 \& %h = ( \*(AqA\*(Aq => 42 );
169 .Ve
170 .PP
171 (at least in platforms of ASCII progeny) Perl 5.8.1 restores the
172 more natural interpretation
173 .PP
174 .Vb 1
175 \& %h = ( \*(Aqv65\*(Aq => 42 );
176 .Ve
177 .PP
178 The multi\-number v\-strings like v65.66 and 65.66.67 still continue to
179 be v\-strings in Perl 5.8.
180 .SS "(Win32) The \-C Switch Has Been Repurposed"
181 .IX Subsection "(Win32) The -C Switch Has Been Repurposed"
182 The \-C switch has changed in an incompatible way. The old semantics
183 of this switch only made sense in Win32 and only in the "use utf8"
184 universe in 5.6.x releases, and do not make sense for the Unicode
185 implementation in 5.8.0. Since this switch could not have been used
186 by anyone, it has been repurposed. The behavior that this switch
187 enabled in 5.6.x releases may be supported in a transparent,
188 data\-dependent fashion in a future release.
189 .PP
190 For the new life of this switch, see "UTF\-8 no longer default under
191 UTF\-8 locales", and "\-C" in perlrun.
192 .SS "(Win32) The /d Switch Of cmd.exe"
193 .IX Subsection "(Win32) The /d Switch Of cmd.exe"
194 Perl 5.8.1 uses the /d switch when running the cmd.exe shell
195 internally for \fBsystem()\fR, backticks, and when opening pipes to external
196 programs. The extra switch disables the execution of AutoRun commands
197 from the registry, which is generally considered undesirable when
198 running external programs. If you wish to retain compatibility with
199 the older behavior, set PERL5SHELL in your environment to \f(CW\*(C`cmd /x/c\*(C'\fR.
200 .SH "Core Enhancements"
201 .IX Header "Core Enhancements"
202 .SS "UTF\-8 no longer default under UTF\-8 locales"
203 .IX Subsection "UTF-8 no longer default under UTF-8 locales"
204 In Perl 5.8.0 many Unicode features were introduced. One of them
205 was found to be of more nuisance than benefit: the automagic
206 (and silent) "UTF\-8\-ification" of filehandles, including the
207 standard filehandles, if the user\*(Aqs locale settings indicated
208 use of UTF\-8.
209 .PP
210 For example, if you had \f(CW\*(C`en_US.UTF\-8\*(C'\fR as your locale, your STDIN and
211 STDOUT were automatically "UTF\-8", in other words an implicit
212 binmode(..., ":utf8") was made. This meant that trying to print, say,
213 \&\fBchr\fR\|(0xff), ended up printing the bytes 0xc3 0xbf. Hardly what
214 you had in mind unless you were aware of this feature of Perl 5.8.0.
215 The problem is that the vast majority of people weren\*(Aqt: for example
216 in RedHat releases 8 and 9 the \fBdefault\fR locale setting is UTF\-8, so
217 all RedHat users got UTF\-8 filehandles, whether they wanted it or not.
218 The pain was intensified by the Unicode implementation of Perl 5.8.0
219 (still) having nasty bugs, especially related to the use of s/// and
220 tr///. (Bugs that have been fixed in 5.8.1)
221 .PP
222 Therefore a decision was made to backtrack the feature and change it
223 from implicit silent default to explicit conscious option. The new
224 Perl command line option \f(CW\*(C`\-C\*(C'\fR and its counterpart environment
225 variable PERL_UNICODE can now be used to control how Perl and Unicode
226 interact at interfaces like I/O and for example the command line
227 arguments. See "\-C" in perlrun and "PERL_UNICODE" in perlrun for more
228 information.
229 .SS "Unsafe signals again available"
230 .IX Subsection "Unsafe signals again available"
231 In Perl 5.8.0 the so\-called "safe signals" were introduced. This
232 means that Perl no longer handles signals immediately but instead
233 "between opcodes", when it is safe to do so. The earlier immediate
234 handling easily could corrupt the internal state of Perl, resulting
235 in mysterious crashes.
236 .PP
237 However, the new safer model has its problems too. Because now an
238 opcode, a basic unit of Perl execution, is never interrupted but
239 instead let to run to completion, certain operations that can take a
240 long time now really do take a long time. For example, certain
241 network operations have their own blocking and timeout mechanisms, and
242 being able to interrupt them immediately would be nice.
243 .PP
244 Therefore perl 5.8.1 introduces a "backdoor" to restore the pre\-5.8.0
245 (pre\-5.7.3, really) signal behaviour. Just set the environment variable
246 PERL_SIGNALS to \f(CW\*(C`unsafe\*(C'\fR, and the old immediate (and unsafe)
247 signal handling behaviour returns. See "PERL_SIGNALS" in perlrun
248 and "Deferred Signals (Safe Signals)" in perlipc.
249 .PP
250 In completely unrelated news, you can now use safe signals with
251 POSIX::SigAction. See "POSIX::SigAction" in POSIX.
252 .SS "Tied Arrays with Negative Array Indices"
253 .IX Subsection "Tied Arrays with Negative Array Indices"
254 Formerly, the indices passed to \f(CW\*(C`FETCH\*(C'\fR, \f(CW\*(C`STORE\*(C'\fR, \f(CW\*(C`EXISTS\*(C'\fR, and
255 \&\f(CW\*(C`DELETE\*(C'\fR methods in tied array class were always non\-negative. If
256 the actual argument was negative, Perl would call FETCHSIZE implicitly
257 and add the result to the index before passing the result to the tied
258 array method. This behaviour is now optional. If the tied array class
259 contains a package variable named \f(CW$NEGATIVE_INDICES\fR which is set to
260 a true value, negative values will be passed to \f(CW\*(C`FETCH\*(C'\fR, \f(CW\*(C`STORE\*(C'\fR,
261 \&\f(CW\*(C`EXISTS\*(C'\fR, and \f(CW\*(C`DELETE\*(C'\fR unchanged.
262 .SS "local ${$x}"
263 .IX Subsection "local ${$x}"
264 The syntaxes
265 .PP
266 .Vb 3
267 \& local ${$x}
268 \& local @{$x}
269 \& local %{$x}
270 .Ve
271 .PP
272 now do localise variables, given that the \f(CW$x\fR is a valid variable name.
273 .SS "Unicode Character Database 4.0.0"
274 .IX Subsection "Unicode Character Database 4.0.0"
275 The copy of the Unicode Character Database included in Perl 5.8 has
276 been updated to 4.0.0 from 3.2.0. This means for example that the
277 Unicode character properties are as in Unicode 4.0.0.
278 .SS "Deprecation Warnings"
279 .IX Subsection "Deprecation Warnings"
280 There is one new feature deprecation. Perl 5.8.0 forgot to add
281 some deprecation warnings, these warnings have now been added.
282 Finally, a reminder of an impending feature removal.
283 .PP
284 \fI(Reminder) Pseudo\-hashes are deprecated (really)\fR
285 .IX Subsection "(Reminder) Pseudo-hashes are deprecated (really)"
286 .PP
287 Pseudo\-hashes were deprecated in Perl 5.8.0 and will be removed in
288 Perl 5.10.0, see perl58delta for details. Each attempt to access
289 pseudo\-hashes will trigger the warning \f(CW\*(C`Pseudo\-hashes are deprecated\*(C'\fR.
290 If you really want to continue using pseudo\-hashes but not to see the
291 deprecation warnings, use:
292 .PP
293 .Vb 1
294 \& no warnings \*(Aqdeprecated\*(Aq;
295 .Ve
296 .PP
297 Or you can continue to use the fields pragma, but please don\*(Aqt
298 expect the data structures to be pseudohashes any more.
299 .PP
300 \fI(Reminder) 5.005\-style threads are deprecated (really)\fR
301 .IX Subsection "(Reminder) 5.005-style threads are deprecated (really)"
302 .PP
303 5.005\-style threads (activated by \f(CW\*(C`use Thread;\*(C'\fR) were deprecated in
304 Perl 5.8.0 and will be removed after Perl 5.8, see perl58delta for
305 details. Each 5.005\-style thread creation will trigger the warning
306 \&\f(CW\*(C`5.005 threads are deprecated\*(C'\fR. If you really want to continue
307 using the 5.005 threads but not to see the deprecation warnings, use:
308 .PP
309 .Vb 1
310 \& no warnings \*(Aqdeprecated\*(Aq;
311 .Ve
312 .PP
313 \fI(Reminder) The $* variable is deprecated (really)\fR
314 .IX Subsection "(Reminder) The $* variable is deprecated (really)"
315 .PP
316 The \f(CW$*\fR variable controlling multi\-line matching has been deprecated
317 and will be removed after 5.8. The variable has been deprecated for a
318 long time, and a deprecation warning \f(CW\*(C`Use of $* is deprecated\*(C'\fR is given,
319 now the variable will just finally be removed. The functionality has
320 been supplanted by the \f(CW\*(C`/s\*(C'\fR and \f(CW\*(C`/m\*(C'\fR modifiers on pattern matching.
321 If you really want to continue using the \f(CW$*\fR\-variable but not to see
322 the deprecation warnings, use:
323 .PP
324 .Vb 1
325 \& no warnings \*(Aqdeprecated\*(Aq;
326 .Ve
327 .SS "Miscellaneous Enhancements"
328 .IX Subsection "Miscellaneous Enhancements"
329 \&\f(CW\*(C`map\*(C'\fR in void context is no longer expensive. \f(CW\*(C`map\*(C'\fR is now context
330 aware, and will not construct a list if called in void context.
331 .PP
332 If a socket gets closed by the server while printing to it, the client
333 now gets a SIGPIPE. While this new feature was not planned, it fell
334 naturally out of PerlIO changes, and is to be considered an accidental
335 feature.
336 .PP
337 PerlIO::get_layers(FH) returns the names of the PerlIO layers
338 active on a filehandle.
339 .PP
340 PerlIO::via layers can now have an optional UTF8 method to
341 indicate whether the layer wants to "auto\-:utf8" the stream.
342 .PP
343 \&\fButf8::is_utf8()\fR has been added as a quick way to test whether
344 a scalar is encoded internally in UTF\-8 (Unicode).
345 .SH "Modules and Pragmata"
346 .IX Header "Modules and Pragmata"
347 .SS "Updated Modules And Pragmata"
348 .IX Subsection "Updated Modules And Pragmata"
349 The following modules and pragmata have been updated since Perl 5.8.0:
350 .IP base 4
351 .IX Item "base"
352 .PD 0
353 .IP B::Bytecode 4
354 .IX Item "B::Bytecode"
355 .PD
356 In much better shape than it used to be. Still far from perfect, but
357 maybe worth a try.
358 .IP B::Concise 4
359 .IX Item "B::Concise"
360 .PD 0
361 .IP B::Deparse 4
362 .IX Item "B::Deparse"
363 .IP Benchmark 4
364 .IX Item "Benchmark"
365 .PD
366 An optional feature, \f(CW\*(C`:hireswallclock\*(C'\fR, now allows for high
367 resolution wall clock times (uses Time::HiRes).
368 .IP ByteLoader 4
369 .IX Item "ByteLoader"
370 See B::Bytecode.
371 .IP bytes 4
372 .IX Item "bytes"
373 Now has bytes::substr.
374 .IP CGI 4
375 .IX Item "CGI"
376 .PD 0
377 .IP charnames 4
378 .IX Item "charnames"
379 .PD
380 One can now have custom character name aliases.
381 .IP CPAN 4
382 .IX Item "CPAN"
383 There is now a simple command line frontend to the CPAN.pm
384 module called \fIcpan\fR.
385 .IP Data::Dumper 4
386 .IX Item "Data::Dumper"
387 A new option, Pair, allows choosing the separator between hash keys
388 and values.
389 .IP DB_File 4
390 .IX Item "DB_File"
391 .PD 0
392 .IP Devel::PPPort 4
393 .IX Item "Devel::PPPort"
394 .IP Digest::MD5 4
395 .IX Item "Digest::MD5"
396 .IP Encode 4
397 .IX Item "Encode"
398 .PD
399 Significant updates on the encoding pragma functionality
400 (tr/// and the DATA filehandle, formats).
401 .Sp
402 If a filehandle has been marked as to have an encoding, unmappable
403 characters are detected already during input, not later (when the
404 corrupted data is being used).
405 .Sp
406 The ISO 8859\-6 conversion table has been corrected (the 0x30..0x39
407 erroneously mapped to U+0660..U+0669, instead of U+0030..U+0039). The
408 GSM 03.38 conversion did not handle escape sequences correctly. The
409 UTF\-7 encoding has been added (making Encode feature\-complete with
410 Unicode::String).
411 .IP fields 4
412 .IX Item "fields"
413 .PD 0
414 .IP libnet 4
415 .IX Item "libnet"
416 .IP Math::BigInt 4
417 .IX Item "Math::BigInt"
418 .PD
419 A lot of bugs have been fixed since v1.60, the version included in Perl
420 v5.8.0. Especially noteworthy are the bug in Calc that caused div and mod to
421 fail for some large values, and the fixes to the handling of bad inputs.
422 .Sp
423 Some new features were added, e.g. the \fBbroot()\fR method, you can now pass
424 parameters to \fBconfig()\fR to change some settings at runtime, and it is now
425 possible to trap the creation of NaN and infinity.
426 .Sp
427 As usual, some optimizations took place and made the math overall a tad
428 faster. In some cases, quite a lot faster, actually. Especially alternative
429 libraries like Math::BigInt::GMP benefit from this. In addition, a lot of the
430 quite clunky routines like \fBfsqrt()\fR and \fBflog()\fR are now much much faster.
431 .IP MIME::Base64 4
432 .IX Item "MIME::Base64"
433 .PD 0
434 .IP NEXT 4
435 .IX Item "NEXT"
436 .PD
437 Diamond inheritance now works.
438 .IP Net::Ping 4
439 .IX Item "Net::Ping"
440 .PD 0
441 .IP PerlIO::scalar 4
442 .IX Item "PerlIO::scalar"
443 .PD
444 Reading from non\-string scalars (like the special variables, see
445 perlvar) now works.
446 .IP podlators 4
447 .IX Item "podlators"
448 .PD 0
449 .IP Pod::LaTeX 4
450 .IX Item "Pod::LaTeX"
451 .IP PodParsers 4
452 .IX Item "PodParsers"
453 .IP Pod::Perldoc 4
454 .IX Item "Pod::Perldoc"
455 .PD
456 Complete rewrite. As a side\-effect, no longer refuses to startup when
457 run by root.
458 .IP Scalar::Util 4
459 .IX Item "Scalar::Util"
460 New utilities: refaddr, isvstring, looks_like_number, set_prototype.
461 .IP Storable 4
462 .IX Item "Storable"
463 Can now store code references (via B::Deparse, so not foolproof).
464 .IP strict 4
465 .IX Item "strict"
466 Earlier versions of the strict pragma did not check the parameters
467 implicitly passed to its "import" (use) and "unimport" (no) routine.
468 This caused the false idiom such as:
469 .Sp
470 .Vb 2
471 \& use strict qw(@ISA);
472 \& @ISA = qw(Foo);
473 .Ve
474 .Sp
475 This however (probably) raised the false expectation that the strict
476 refs, vars and subs were being enforced (and that \f(CW@ISA\fR was somehow
477 "declared"). But the strict refs, vars, and subs are \fBnot\fR enforced
478 when using this false idiom.
479 .Sp
480 Starting from Perl 5.8.1, the above \fBwill\fR cause an error to be
481 raised. This may cause programs which used to execute seemingly
482 correctly without warnings and errors to fail when run under 5.8.1.
483 This happens because
484 .Sp
485 .Vb 1
486 \& use strict qw(@ISA);
487 .Ve
488 .Sp
489 will now fail with the error:
490 .Sp
491 .Vb 1
492 \& Unknown \*(Aqstrict\*(Aq tag(s) \*(Aq@ISA\*(Aq
493 .Ve
494 .Sp
495 The remedy to this problem is to replace this code with the correct idiom:
496 .Sp
497 .Vb 3
498 \& use strict;
499 \& use vars qw(@ISA);
500 \& @ISA = qw(Foo);
501 .Ve
502 .IP Term::ANSIcolor 4
503 .IX Item "Term::ANSIcolor"
504 .PD 0
505 .IP Test::Harness 4
506 .IX Item "Test::Harness"
507 .PD
508 Now much more picky about extra or missing output from test scripts.
509 .IP Test::More 4
510 .IX Item "Test::More"
511 .PD 0
512 .IP Test::Simple 4
513 .IX Item "Test::Simple"
514 .IP Text::Balanced 4
515 .IX Item "Text::Balanced"
516 .IP Time::HiRes 4
517 .IX Item "Time::HiRes"
518 .PD
519 Use of \fBnanosleep()\fR, if available, allows mixing subsecond sleeps with
520 alarms.
521 .IP threads 4
522 .IX Item "threads"
523 Several fixes, for example for \fBjoin()\fR problems and memory
524 leaks. In some platforms (like Linux) that use glibc the minimum memory
525 footprint of one ithread has been reduced by several hundred kilobytes.
526 .IP threads::shared 4
527 .IX Item "threads::shared"
528 Many memory leaks have been fixed.
529 .IP Unicode::Collate 4
530 .IX Item "Unicode::Collate"
531 .PD 0
532 .IP Unicode::Normalize 4
533 .IX Item "Unicode::Normalize"
534 .IP Win32::GetFolderPath 4
535 .IX Item "Win32::GetFolderPath"
536 .IP Win32::GetOSVersion 4
537 .IX Item "Win32::GetOSVersion"
538 .PD
539 Now returns extra information.
540 .SH "Utility Changes"
541 .IX Header "Utility Changes"
542 The \f(CW\*(C`h2xs\*(C'\fR utility now produces a more modern layout:
543 \&\fIFoo\-Bar/lib/Foo/Bar.pm\fR instead of \fIFoo/Bar/Bar.pm\fR.
544 Also, the boilerplate test is now called \fIt/Foo\-Bar.t\fR
545 instead of \fIt/1.t\fR.
546 .PP
547 The Perl debugger (\fIlib/perl5db.pl\fR) has now been extensively
548 documented and bugs found while documenting have been fixed.
549 .PP
550 \&\f(CW\*(C`perldoc\*(C'\fR has been rewritten from scratch to be more robust and
551 feature rich.
552 .PP
553 \&\f(CW\*(C`perlcc \-B\*(C'\fR works now at least somewhat better, while \f(CW\*(C`perlcc \-c\*(C'\fR
554 is rather more broken. (The Perl compiler suite as a whole continues
555 to be experimental.)
556 .SH "New Documentation"
557 .IX Header "New Documentation"
558 perl573delta has been added to list the differences between the
559 (now quite obsolete) development releases 5.7.2 and 5.7.3.
560 .PP
561 perl58delta has been added: it is the perldelta of 5.8.0, detailing
562 the differences between 5.6.0 and 5.8.0.
563 .PP
564 perlartistic has been added: it is the Artistic License in pod format,
565 making it easier for modules to refer to it.
566 .PP
567 perlcheat has been added: it is a Perl cheat sheet.
568 .PP
569 perlgpl has been added: it is the GNU General Public License in pod
570 format, making it easier for modules to refer to it.
571 .PP
572 perlmacosx has been added to tell about the installation and use
573 of Perl in Mac OS X.
574 .PP
575 perlos400 has been added to tell about the installation and use
576 of Perl in OS/400 PASE.
577 .PP
578 perlreref has been added: it is a regular expressions quick reference.
579 .SH "Installation and Configuration Improvements"
580 .IX Header "Installation and Configuration Improvements"
581 The Unix standard Perl location, \fI/usr/bin/perl\fR, is no longer
582 overwritten by default if it exists. This change was very prudent
583 because so many Unix vendors already provide a \fI/usr/bin/perl\fR,
584 but simultaneously many system utilities may depend on that
585 exact version of Perl, so better not to overwrite it.
586 .PP
587 One can now specify installation directories for site and vendor man
588 and HTML pages, and site and vendor scripts. See \fIINSTALL\fR.
589 .PP
590 One can now specify a destination directory for Perl installation
591 by specifying the DESTDIR variable for \f(CW\*(C`make install\*(C'\fR. (This feature
592 is slightly different from the previous \f(CW\*(C`Configure \-Dinstallprefix=...\*(C'\fR.)
593 See \fIINSTALL\fR.
594 .PP
595 gcc versions 3.x introduced a new warning that caused a lot of noise
596 during Perl compilation: \f(CW\*(C`gcc \-Ialreadyknowndirectory (warning:
597 changing search order)\*(C'\fR. This warning has now been avoided by
598 Configure weeding out such directories before the compilation.
599 .PP
600 One can now build subsets of Perl core modules by using the
601 Configure flags \f(CW\*(C`\-Dnoextensions=...\*(C'\fR and \f(CW\*(C`\-Donlyextensions=...\*(C'\fR,
602 see \fIINSTALL\fR.
603 .SS "Platform\-specific enhancements"
604 .IX Subsection "Platform-specific enhancements"
605 In Cygwin Perl can now be built with threads (\f(CW\*(C`Configure \-Duseithreads\*(C'\fR).
606 This works with both Cygwin 1.3.22 and Cygwin 1.5.3.
607 .PP
608 In newer FreeBSD releases Perl 5.8.0 compilation failed because of
609 trying to use \fImalloc.h\fR, which in FreeBSD is just a dummy file, and
610 a fatal error to even try to use. Now \fImalloc.h\fR is not used.
611 .PP
612 Perl is now known to build also in Hitachi HI\-UXMPP.
613 .PP
614 Perl is now known to build again in LynxOS.
615 .PP
616 Mac OS X now installs with Perl version number embedded in
617 installation directory names for easier upgrading of user\-compiled
618 Perl, and the installation directories in general are more standard.
619 In other words, the default installation no longer breaks the
620 Apple\-provided Perl. On the other hand, with \f(CW\*(C`Configure \-Dprefix=/usr\*(C'\fR
621 you can now really replace the Apple\-supplied Perl (\fBplease be careful\fR).
622 .PP
623 Mac OS X now builds Perl statically by default. This change was done
624 mainly for faster startup times. The Apple\-provided Perl is still
625 dynamically linked and shared, and you can enable the sharedness for
626 your own Perl builds by \f(CW\*(C`Configure \-Duseshrplib\*(C'\fR.
627 .PP
628 Perl has been ported to IBM\*(Aqs OS/400 PASE environment. The best way
629 to build a Perl for PASE is to use an AIX host as a cross\-compilation
630 environment. See README.os400.
631 .PP
632 Yet another cross\-compilation option has been added: now Perl builds
633 on OpenZaurus, a Linux distribution based on Mandrake + Embedix for
634 the Sharp Zaurus PDA. See the Cross/README file.
635 .PP
636 Tru64 when using gcc 3 drops the optimisation for \fItoke.c\fR to \f(CW\*(C`\-O2\*(C'\fR
637 because of gigantic memory use with the default \f(CW\*(C`\-O3\*(C'\fR.
638 .PP
639 Tru64 can now build Perl with the newer Berkeley DBs.
640 .PP
641 Building Perl on WinCE has been much enhanced, see \fIREADME.ce\fR
642 and \fIREADME.perlce\fR.
643 .SH "Selected Bug Fixes"
644 .IX Header "Selected Bug Fixes"
645 .SS "Closures, eval and lexicals"
646 .IX Subsection "Closures, eval and lexicals"
647 There have been many fixes in the area of anonymous subs, lexicals and
648 closures. Although this means that Perl is now more "correct", it is
649 possible that some existing code will break that happens to rely on
650 the faulty behaviour. In practice this is unlikely unless your code
651 contains a very complex nesting of anonymous subs, evals and lexicals.
652 .SS "Generic fixes"
653 .IX Subsection "Generic fixes"
654 If an input filehandle is marked \f(CW\*(C`:utf8\*(C'\fR and Perl sees illegal UTF\-8
655 coming in when doing \f(CW\*(C`<FH>\*(C'\fR, if warnings are enabled a warning is
656 immediately given \- instead of being silent about it and Perl being
657 unhappy about the broken data later. (The \f(CW:encoding(utf8)\fR layer
658 also works the same way.)
659 .PP
660 binmode(SOCKET, ":utf8") only worked on the input side, not on the
661 output side of the socket. Now it works both ways.
662 .PP
663 For threaded Perls certain system database functions like \fBgetpwent()\fR
664 and \fBgetgrent()\fR now grow their result buffer dynamically, instead of
665 failing. This means that at sites with lots of users and groups the
666 functions no longer fail by returning only partial results.
667 .PP
668 Perl 5.8.0 had accidentally broken the capability for users
669 to define their own uppercase<\->lowercase Unicode mappings
670 (as advertised by the Camel). This feature has been fixed and
671 is also documented better.
672 .PP
673 In 5.8.0 this
674 .PP
675 .Vb 1
676 \& $some_unicode .= <FH>;
677 .Ve
678 .PP
679 didn\*(Aqt work correctly but instead corrupted the data. This has now
680 been fixed.
681 .PP
682 Tied methods like FETCH etc. may now safely access tied values, i.e.
683 resulting in a recursive call to FETCH etc. Remember to break the
684 recursion, though.
685 .PP
686 At startup Perl blocks the SIGFPE signal away since there isn\*(Aqt much
687 Perl can do about it. Previously this blocking was in effect also for
688 programs executed from within Perl. Now Perl restores the original
689 SIGFPE handling routine, whatever it was, before running external
690 programs.
691 .PP
692 Linenumbers in Perl scripts may now be greater than 65536, or 2**16.
693 (Perl scripts have always been able to be larger than that, it\*(Aqs just
694 that the linenumber for reported errors and warnings have "wrapped
695 around".) While scripts that large usually indicate a need to rethink
696 your code a bit, such Perl scripts do exist, for example as results
697 from generated code. Now linenumbers can go all the way to
698 4294967296, or 2**32.
699 .SS "Platform\-specific fixes"
700 .IX Subsection "Platform-specific fixes"
701 Linux
702 .IP \(bu 4
703 Setting \f(CW$0\fR works again (with certain limitations that
704 Perl cannot do much about: see "$0" in perlvar)
705 .PP
706 HP\-UX
707 .IP \(bu 4
708 Setting \f(CW$0\fR now works.
709 .PP
710 VMS
711 .IP \(bu 4
712 Configuration now tests for the presence of \f(CWpoll()\fR, and IO::Poll
713 now uses the vendor\-supplied function if detected.
714 .IP \(bu 4
715 A rare access violation at Perl start\-up could occur if the Perl image was
716 installed with privileges or if there was an identifier with the
717 subsystem attribute set in the process\*(Aqs rightslist. Either of these
718 circumstances triggered tainting code that contained a pointer bug.
719 The faulty pointer arithmetic has been fixed.
720 .IP \(bu 4
721 The length limit on values (not keys) in the \f(CW%ENV\fR hash has been raised
722 from 255 bytes to 32640 bytes (except when the PERL_ENV_TABLES setting
723 overrides the default use of logical names for \f(CW%ENV\fR). If it is
724 necessary to access these long values from outside Perl, be aware that
725 they are implemented using search list logical names that store the
726 value in pieces, each 255\-byte piece (up to 128 of them) being an
727 element in the search list. When doing a lookup in \f(CW%ENV\fR from within
728 Perl, the elements are combined into a single value. The existing
729 VMS\-specific ability to access individual elements of a search list
730 logical name via the \f(CW$ENV\fR{\*(Aqfoo;N\*(Aq} syntax (where N is the search list
731 index) is unimpaired.
732 .IP \(bu 4
733 The piping implementation now uses local rather than global DCL
734 symbols for inter\-process communication.
735 .IP \(bu 4
736 File::Find could become confused when navigating to a relative
737 directory whose name collided with a logical name. This problem has
738 been corrected by adding directory syntax to relative path names, thus
739 preventing logical name translation.
740 .PP
741 Win32
742 .IP \(bu 4
743 A memory leak in the \fBfork()\fR emulation has been fixed.
744 .IP \(bu 4
745 The return value of the \fBioctl()\fR built\-in function was accidentally
746 broken in 5.8.0. This has been corrected.
747 .IP \(bu 4
748 The internal message loop executed by perl during blocking operations
749 sometimes interfered with messages that were external to Perl.
750 This often resulted in blocking operations terminating prematurely or
751 returning incorrect results, when Perl was executing under environments
752 that could generate Windows messages. This has been corrected.
753 .IP \(bu 4
754 Pipes and sockets are now automatically in binary mode.
755 .IP \(bu 4
756 The four\-argument form of \fBselect()\fR did not preserve $! (errno) properly
757 when there were errors in the underlying call. This is now fixed.
758 .IP \(bu 4
759 The "CR CR LF" problem of has been fixed, binmode(FH, ":crlf")
760 is now effectively a no\-op.
761 .SH "New or Changed Diagnostics"
762 .IX Header "New or Changed Diagnostics"
763 All the warnings related to \fBpack()\fR and \fBunpack()\fR were made more
764 informative and consistent.
765 .ie n .SS "Changed ""A thread exited while %d threads were running"""
766 .el .SS "Changed ""A thread exited while \f(CW%d\fP threads were running"""
767 .IX Subsection "Changed ""A thread exited while %d threads were running"""
768 The old version
769 .PP
770 .Vb 1
771 \& A thread exited while %d other threads were still running
772 .Ve
773 .PP
774 was misleading because the "other" included also the thread giving
775 the warning.
776 .SS "Removed ""Attempt to clear a restricted hash"""
777 .IX Subsection "Removed ""Attempt to clear a restricted hash"""
778 It is not illegal to clear a restricted hash, so the warning
779 was removed.
780 .SS "New ""Illegal declaration of anonymous subroutine"""
781 .IX Subsection "New ""Illegal declaration of anonymous subroutine"""
782 You must specify the block of code for \f(CW\*(C`sub\*(C'\fR.
783 .SS "Changed ""Invalid range ""%s"" in transliteration operator"""
784 .IX Subsection "Changed ""Invalid range ""%s"" in transliteration operator"""
785 The old version
786 .PP
787 .Vb 1
788 \& Invalid [] range "%s" in transliteration operator
789 .Ve
790 .PP
791 was simply wrong because there are no "[] ranges" in tr///.
792 .SS "New ""Missing control char name in \ec"""
793 .IX Subsection "New ""Missing control char name in c"""
794 Self\-explanatory.
795 .ie n .SS "New ""Newline in left\-justified string for %s"""
796 .el .SS "New ""Newline in left\-justified string for \f(CW%s\fP"""
797 .IX Subsection "New ""Newline in left-justified string for %s"""
798 The padding spaces would appear after the newline, which is
799 probably not what you had in mind.
800 .ie n .SS "New ""Possible precedence problem on bitwise %c operator"""
801 .el .SS "New ""Possible precedence problem on bitwise \f(CW%c\fP operator"""
802 .IX Subsection "New ""Possible precedence problem on bitwise %c operator"""
803 If you think this
804 .PP
805 .Vb 1
806 \& $x & $y == 0
807 .Ve
808 .PP
809 tests whether the bitwise AND of \f(CW$x\fR and \f(CW$y\fR is zero,
810 you will like this warning.
811 .SS "New ""Pseudo\-hashes are deprecated"""
812 .IX Subsection "New ""Pseudo-hashes are deprecated"""
813 This warning should have been already in 5.8.0, since they are.
814 .ie n .SS "New ""\fBread()\fP on %s filehandle %s"""
815 .el .SS "New ""\fBread()\fP on \f(CW%s\fP filehandle \f(CW%s\fP"""
816 .IX Subsection "New ""read() on %s filehandle %s"""
817 You cannot \fBread()\fR (or \fBsysread()\fR) from a closed or unopened filehandle.
818 .SS "New ""5.005 threads are deprecated"""
819 .IX Subsection "New ""5.005 threads are deprecated"""
820 This warning should have been already in 5.8.0, since they are.
821 .SS "New ""Tied variable freed while still in use"""
822 .IX Subsection "New ""Tied variable freed while still in use"""
823 Something pulled the plug on a live tied variable, Perl plays
824 safe by bailing out.
825 .SS "New ""To%s: illegal mapping \*(Aq%s\*(Aq"""
826 .IX Subsection "New ""To%s: illegal mapping '%s'"""
827 An illegal user\-defined Unicode casemapping was specified.
828 .SS "New ""Use of freed value in iteration"""
829 .IX Subsection "New ""Use of freed value in iteration"""
830 Something modified the values being iterated over. This is not good.
831 .SH "Changed Internals"
832 .IX Header "Changed Internals"
833 These news matter to you only if you either write XS code or like to
834 know about or hack Perl internals (using Devel::Peek or any of the
835 \&\f(CW\*(C`B::\*(C'\fR modules counts), or like to run Perl with the \f(CW\*(C`\-D\*(C'\fR option.
836 .PP
837 The embedding examples of perlembed have been reviewed to be
838 up to date and consistent: for example, the correct use of
839 \&\fBPERL_SYS_INIT3()\fR and \fBPERL_SYS_TERM()\fR.
840 .PP
841 Extensive reworking of the pad code (the code responsible
842 for lexical variables) has been conducted by Dave Mitchell.
843 .PP
844 Extensive work on the v\-strings by John Peacock.
845 .PP
846 UTF\-8 length and position cache: to speed up the handling of Unicode
847 (UTF\-8) scalars, a cache was introduced. Potential problems exist if
848 an extension bypasses the official APIs and directly modifies the PV
849 of an SV: the UTF\-8 cache does not get cleared as it should.
850 .PP
851 APIs obsoleted in Perl 5.8.0, like sv_2pv, sv_catpvn, sv_catsv,
852 sv_setsv, are again available.
853 .PP
854 Certain Perl core C APIs like cxinc and regatom are no longer
855 available at all to code outside the Perl core of the Perl core
856 extensions. This is intentional. They never should have been
857 available with the shorter names, and if your application depends on
858 them, you should (be ashamed and) contact perl5\-porters to discuss
859 what are the proper APIs.
860 .PP
861 Certain Perl core C APIs like \f(CW\*(C`Perl_list\*(C'\fR are no longer available
862 without their \f(CW\*(C`Perl_\*(C'\fR prefix. If your XS module stops working
863 because some functions cannot be found, in many cases a simple fix is
864 to add the \f(CW\*(C`Perl_\*(C'\fR prefix to the function and the thread context
865 \&\f(CW\*(C`aTHX_\*(C'\fR as the first argument of the function call. This is also how
866 it should always have been done: letting the Perl_\-less forms to leak
867 from the core was an accident. For cleaner embedding you can also
868 force this for all APIs by defining at compile time the cpp define
869 PERL_NO_SHORT_NAMES.
870 .PP
871 \&\fBPerl_save_bool()\fR has been added.
872 .PP
873 Regexp objects (those created with \f(CW\*(C`qr\*(C'\fR) now have S\-magic rather than
874 R\-magic. This fixed regexps of the form /...(??{...;$x})/ to no
875 longer ignore changes made to \f(CW$x\fR. The S\-magic avoids dropping
876 the caching optimization and making (??{...}) constructs obscenely
877 slow (and consequently useless). See also "Magic Variables" in perlguts.
878 Regexp::Copy was affected by this change.
879 .PP
880 The Perl internal debugging macros \fBDEBUG()\fR and \fBDEB()\fR have been renamed
881 to \fBPERL_DEBUG()\fR and \fBPERL_DEB()\fR to avoid namespace conflicts.
882 .PP
883 \&\f(CW\*(C`\-DL\*(C'\fR removed (the leaktest had been broken and unsupported for years,
884 use alternative debugging mallocs or tools like valgrind and Purify).
885 .PP
886 Verbose modifier \f(CW\*(C`v\*(C'\fR added for \f(CW\*(C`\-DXv\*(C'\fR and \f(CW\*(C`\-Dsv\*(C'\fR, see perlrun.
887 .SH "New Tests"
888 .IX Header "New Tests"
889 In Perl 5.8.0 there were about 69000 separate tests in about 700 test files,
890 in Perl 5.8.1 there are about 77000 separate tests in about 780 test files.
891 The exact numbers depend on the Perl configuration and on the operating
892 system platform.
893 .SH "Known Problems"
894 .IX Header "Known Problems"
895 The hash randomisation mentioned in "Incompatible Changes" is definitely
896 problematic: it will wake dormant bugs and shake out bad assumptions.
897 .PP
898 If you want to use mod_perl 2.x with Perl 5.8.1, you will need
899 mod_perl\-1.99_10 or higher. Earlier versions of mod_perl 2.x
900 do not work with the randomised hashes. (mod_perl 1.x works fine.)
901 You will also need Apache::Test 1.04 or higher.
902 .PP
903 Many of the rarer platforms that worked 100% or pretty close to it
904 with perl 5.8.0 have been left a little bit untended since their
905 maintainers have been otherwise busy lately, and therefore there will
906 be more failures on those platforms. Such platforms include Mac OS
907 Classic, IBM z/OS (and other EBCDIC platforms), and NetWare. The most
908 common Perl platforms (Unix and Unix\-like, Microsoft platforms, and
909 VMS) have large enough testing and expert population that they are
910 doing well.
911 .SS "Tied hashes in scalar context"
912 .IX Subsection "Tied hashes in scalar context"
913 Tied hashes do not currently return anything useful in scalar context,
914 for example when used as boolean tests:
915 .PP
916 .Vb 1
917 \& if (%tied_hash) { ... }
918 .Ve
919 .PP
920 The current nonsensical behaviour is always to return false,
921 regardless of whether the hash is empty or has elements.
922 .PP
923 The root cause is that there is no interface for the implementors of
924 tied hashes to implement the behaviour of a hash in scalar context.
925 .SS "Net::Ping 450_service and 510_ping_udp failures"
926 .IX Subsection "Net::Ping 450_service and 510_ping_udp failures"
927 The subtests 9 and 18 of lib/Net/Ping/t/450_service.t, and the
928 subtest 2 of lib/Net/Ping/t/510_ping_udp.t might fail if you have
929 an unusual networking setup. For example in the latter case the
930 test is trying to send a UDP ping to the IP address 127.0.0.1.
931 .SS B::C
932 .IX Subsection "B::C"
933 The C\-generating compiler backend B::C (the frontend being
934 \&\f(CW\*(C`perlcc \-c\*(C'\fR) is even more broken than it used to be because of
935 the extensive lexical variable changes. (The good news is that
936 B::Bytecode and ByteLoader are better than they used to be.)
937 .SH "Platform Specific Problems"
938 .IX Header "Platform Specific Problems"
939 .SS "EBCDIC Platforms"
940 .IX Subsection "EBCDIC Platforms"
941 IBM z/OS and other EBCDIC platforms continue to be problematic
942 regarding Unicode support. Many Unicode tests are skipped when
943 they really should be fixed.
944 .SS "Cygwin 1.5 problems"
945 .IX Subsection "Cygwin 1.5 problems"
946 In Cygwin 1.5 the \fIio/tell\fR and \fIop/sysio\fR tests have failures for
947 some yet unknown reason. In 1.5.5 the threads tests stress_cv,
948 stress_re, and stress_string are failing unless the environment
949 variable PERLIO is set to "perlio" (which makes also the io/tell
950 failure go away).
951 .PP
952 Perl 5.8.1 does build and work well with Cygwin 1.3: with (uname \-a)
953 \&\f(CW\*(C`CYGWIN_NT\-5.0 ... 1.3.22(0.78/3/2) 2003\-03\-18 09:20 i686 ...\*(C'\fR
954 a 100% "make test" was achieved with \f(CW\*(C`Configure \-des \-Duseithreads\*(C'\fR.
955 .SS "HP\-UX: HP cc warnings about sendfile and sendpath"
956 .IX Subsection "HP-UX: HP cc warnings about sendfile and sendpath"
957 With certain HP C compiler releases (e.g. B.11.11.02) you will
958 get many warnings like this (lines wrapped for easier reading):
959 .PP
960 .Vb 6
961 \& cc: "/usr/include/sys/socket.h", line 504: warning 562:
962 \& Redeclaration of "sendfile" with a different storage class specifier:
963 \& "sendfile" will have internal linkage.
964 \& cc: "/usr/include/sys/socket.h", line 505: warning 562:
965 \& Redeclaration of "sendpath" with a different storage class specifier:
966 \& "sendpath" will have internal linkage.
967 .Ve
968 .PP
969 The warnings show up both during the build of Perl and during certain
970 lib/ExtUtils tests that invoke the C compiler. The warning, however,
971 is not serious and can be ignored.
972 .SS "IRIX: t/uni/tr_7jis.t falsely failing"
973 .IX Subsection "IRIX: t/uni/tr_7jis.t falsely failing"
974 The test t/uni/tr_7jis.t is known to report failure under \*(Aqmake test\*(Aq
975 or the test harness with certain releases of IRIX (at least IRIX 6.5
976 and MIPSpro Compilers Version 7.3.1.1m), but if run manually the test
977 fully passes.
978 .SS "Mac OS X: no usemymalloc"
979 .IX Subsection "Mac OS X: no usemymalloc"
980 The Perl malloc (\f(CW\*(C`\-Dusemymalloc\*(C'\fR) does not work at all in Mac OS X.
981 This is not that serious, though, since the native malloc works just
982 fine.
983 .SS "Tru64: No threaded builds with GNU cc (gcc)"
984 .IX Subsection "Tru64: No threaded builds with GNU cc (gcc)"
985 In the latest Tru64 releases (e.g. v5.1B or later) gcc cannot be used
986 to compile a threaded Perl (\-Duseithreads) because the system
987 \&\f(CW\*(C`<pthread.h>\*(C'\fR file doesn\*(Aqt know about gcc.
988 .SS "Win32: sysopen, sysread, syswrite"
989 .IX Subsection "Win32: sysopen, sysread, syswrite"
990 As of the 5.8.0 release, \fBsysopen()\fR/\fBsysread()\fR/\fBsyswrite()\fR do not behave
991 like they used to in 5.6.1 and earlier with respect to "text" mode.
992 These built\-ins now always operate in "binary" mode (even if \fBsysopen()\fR
993 was passed the O_TEXT flag, or if \fBbinmode()\fR was used on the file
994 handle). Note that this issue should only make a difference for disk
995 files, as sockets and pipes have always been in "binary" mode in the
996 Windows port. As this behavior is currently considered a bug,
997 compatible behavior may be re\-introduced in a future release. Until
998 then, the use of \fBsysopen()\fR, \fBsysread()\fR and \fBsyswrite()\fR is not supported
999 for "text" mode operations.
1000 .SH "Future Directions"
1001 .IX Header "Future Directions"
1002 The following things \fBmight\fR happen in future. The first publicly
1003 available releases having these characteristics will be the developer
1004 releases Perl 5.9.x, culminating in the Perl 5.10.0 release. These
1005 are our best guesses at the moment: we reserve the right to rethink.
1006 .IP \(bu 4
1007 PerlIO will become The Default. Currently (in Perl 5.8.x) the stdio
1008 library is still used if Perl thinks it can use certain tricks to
1009 make stdio go \fBreally\fR fast. For future releases our goal is to
1010 make PerlIO go even faster.
1011 .IP \(bu 4
1012 A new feature called \fIassertions\fR will be available. This means that
1013 one can have code called assertions sprinkled in the code: usually
1014 they are optimised away, but they can be enabled with the \f(CW\*(C`\-A\*(C'\fR option.
1015 .IP \(bu 4
1016 A new operator \f(CW\*(C`//\*(C'\fR (defined\-or) will be available. This means that
1017 one will be able to say
1018 .Sp
1019 .Vb 1
1020 \& $a // $b
1021 .Ve
1022 .Sp
1023 instead of
1024 .Sp
1025 .Vb 1
1026 \& defined $a ? $a : $b
1027 .Ve
1028 .Sp
1029 and
1030 .Sp
1031 .Vb 1
1032 \& $c //= $d;
1033 .Ve
1034 .Sp
1035 instead of
1036 .Sp
1037 .Vb 1
1038 \& $c = $d unless defined $c;
1039 .Ve
1040 .Sp
1041 The operator will have the same precedence and associativity as \f(CW\*(C`||\*(C'\fR.
1042 A source code patch against the Perl 5.8.1 sources will be available
1043 in CPAN as \fIauthors/id/H/HM/HMBRAND/dor\-5.8.1.diff\fR.
1044 .IP \(bu 4
1045 \&\f(CWunpack()\fR will default to unpacking the \f(CW$_\fR.
1046 .IP \(bu 4
1047 Various Copy\-On\-Write techniques will be investigated in hopes
1048 of speeding up Perl.
1049 .IP \(bu 4
1050 CPANPLUS, Inline, and Module::Build will become core modules.
1051 .IP \(bu 4
1052 The ability to write true lexically scoped pragmas will be introduced.
1053 .IP \(bu 4
1054 Work will continue on the bytecompiler and byteloader.
1055 .IP \(bu 4
1056 v\-strings as they currently exist are scheduled to be deprecated. The
1057 v\-less form (1.2.3) will become a "version object" when used with \f(CW\*(C`use\*(C'\fR,
1058 \&\f(CW\*(C`require\*(C'\fR, and \f(CW$VERSION\fR. $^V will also be a "version object" so the
1059 printf("%vd",...) construct will no longer be needed. The v\-ful version
1060 (v1.2.3) will become obsolete. The equivalence of strings and v\-strings (e.g.
1061 that currently 5.8.0 is equal to "\e5\e8\e0") will go away. \fBThere may be no
1062 deprecation warning for v\-strings\fR, though: it is quite hard to detect when
1063 v\-strings are being used safely, and when they are not.
1064 .IP \(bu 4
1065 5.005 Threads Will Be Removed
1066 .IP \(bu 4
1067 The \f(CW$*\fR Variable Will Be Removed
1068 (it was deprecated a long time ago)
1069 .IP \(bu 4
1070 Pseudohashes Will Be Removed
1071 .SH "Reporting Bugs"
1072 .IX Header "Reporting Bugs"
1073 If you find what you think is a bug, you might check the articles
1074 recently posted to the comp.lang.perl.misc newsgroup and the perl
1075 bug database at http://bugs.perl.org/ . There may also be
1076 information at http://www.perl.com/ , the Perl Home Page.
1077 .PP
1078 If you believe you have an unreported bug, please run the \fBperlbug\fR
1079 program included with your release. Be sure to trim your bug down
1080 to a tiny but sufficient test case. Your bug report, along with the
1081 output of \f(CW\*(C`perl \-V\*(C'\fR, will be sent off to [email protected] to be
1082 analysed by the Perl porting team. You can browse and search
1083 the Perl 5 bugs at http://bugs.perl.org/
1084 .SH "SEE ALSO"
1085 .IX Header "SEE ALSO"
1086 The \fIChanges\fR file for exhaustive details on what changed.
1087 .PP
1088 The \fIINSTALL\fR file for how to build Perl.
1089 .PP
1090 The \fIREADME\fR file for general stuff.
1091 .PP
1092 The \fIArtistic\fR and \fICopying\fR files for copyright information.