3 perldelta - what's new for perl5.006 (as of 5.005_56)
7 This document describes differences between the 5.005 release and this one.
9 =head1 Incompatible Changes
11 =head2 Perl Source Incompatibilities
13 None known at this time.
15 =head2 C Source Incompatibilities
21 Release 5.005 grandfathered old global symbol names by providing preprocessor
22 macros for extension source compatibility. As of release 5.006, these
23 preprocessor definitions are not available by default. You need to explicitly
24 compile perl with C<-DPERL_POLLUTE> in order to get these definitions.
26 =item C<PERL_POLLUTE_MALLOC>
28 Enabling the use of Perl's malloc in release 5.005 and earlier caused
29 the namespace of system versions of the malloc family of functions to
30 be usurped by the Perl versions of these functions, since they used the
31 same names by default.
33 Besides causing problems on platforms that do not allow these functions to
34 be cleanly replaced, this also meant that the system versions could not
35 be called in programs that used Perl's malloc. Previous versions of Perl
36 have allowed this behavior to be suppressed with the HIDEMYMALLOC and
37 EMBEDMYMALLOC preprocessor definitions.
39 As of release 5.006, Perl's malloc family of functions have default names
40 distinct from the system versions. You need to explicitly compile perl with
41 C<-DPERL_POLLUTE_MALLOC> in order to get the older behavior. HIDEMYMALLOC
42 and EMBEDMYMALLOC have no effect, since the behavior they enabled is now
45 Note that these functions do B<not> constitute Perl's memory allocation API.
46 See L<perlguts/"Memory Allocation"> for further information about that.
48 =item C<PL_na> and C<dTHR> Issues
50 The C<PL_na> global is now thread local, so a C<dTHR> declaration is needed
51 in the scope in which it appears. XSUBs should handle this automatically,
52 but if you have used C<PL_na> in support functions, you either need to
53 change the C<PL_na> to a local variable (which is recommended), or put in
58 =head2 Compatible C Source API Changes
62 =item C<PATCHLEVEL> is now C<PERL_VERSION>
64 The cpp macros C<PERL_REVISION>, C<PERL_VERSION> and C<PERL_SUBVERSION>
65 are now available by default from perl.h, and reflect the base revision,
66 patchlevel and subversion respectively. C<PERL_REVISION> had no
67 prior equivalent, while C<PERL_VERSION> and C<PERL_SUBVERSION> were
68 previously available as C<PATCHLEVEL> and C<SUBVERSION>.
70 The new names cause less pollution of the cpp namespace, and reflect what
71 the numbers have come to stand for in common practice. For compatibility,
72 the old names are still supported when patchlevel.h is explicitly
73 included (as required before), so there is no source incompatibility
78 =head2 Binary Incompatibilities
80 This release is not binary compatible with the 5.005 release and its
85 =head2 Unicode and UTF-8 support
87 Perl can optionally use UTF-8 as its internal representation for character
88 strings. The C<use utf8> pragma enables this support in the current lexical
89 scope. See L<utf8> for more information.
91 =head2 Lexically scoped warning categories
93 You can now control the granularity of warnings emitted by perl at a finer
94 level using the C<use warning> pragma. See L<warning> for details.
96 =head2 Binary numbers supported
98 Binary numbers are now supported as literals, in s?printf formats, and
102 printf "The answer is: %b\n", oct("0b101010");
104 =head2 syswrite() ease-of-use
106 The length argument of C<syswrite()> is now optional.
108 =head2 64-bit support
110 Better 64-bit support -- but full support still a distant goal. One
111 must Configure with -Duse64bits to get Configure to probe for the
112 extent of 64-bit support. Depending on the platform (hints file) more
113 or less 64-awareness becomes available. As of 5.005_54 at least
114 somewhat 64-bit aware platforms are HP-UX 11 or better, Solaris 2.6 or
115 better, IRIX 6.2 or better. Naturally 64-bit platforms like Digital
116 UNIX and UNICOS also have 64-bit support.
118 =head2 Better syntax checks on parenthesized unary operators
122 print defined(&foo,&bar,&baz);
123 print uc("foo","bar","baz");
126 used to be accidentally allowed in earlier versions, and produced
127 unpredictable behavior. Some of them produced ancillary warnings
128 when used in this way, while others silently did the wrong thing.
130 The parenthesized forms of most unary operators that expect a single
131 argument will now ensure that they are not called with more than one
132 argument, making the above cases syntax errors. Note that the usual
135 print defined &foo, &bar, &baz;
136 print uc "foo", "bar", "baz";
139 remains unchanged. See L<perlop>.
141 =head2 Improved C<qw//> operator
143 The C<qw//> operator is now evaluated at compile time into a true list
144 instead of being replaced with a run time call to C<split()>. This
145 removes the confusing behavior of C<qw//> in scalar context stemming from
146 the older implementation, which inherited the behavior from split().
150 $foo = ($bar) = qw(a b c); print "$foo|$bar\n";
152 now correctly prints "3|a", instead of "2|a".
154 =head2 pack() format 'Z' supported
156 The new format type 'Z' is useful for packing and unpacking null-terminated
157 strings. See L<perlfunc/"pack">.
159 =head2 pack() format modifier '!' supported
161 The new format type modifer '!' is useful for packing and unpacking
162 native shorts, ints, and longs. See L<perlfunc/"pack">.
164 =head2 $^X variables may now have names longer than one character
166 Formerly, $^X was synonymous with ${"\cX"}, but $^XY was a syntax
167 error. Now variable names that begin with a control character may be
168 arbitrarily long. However, for compatibility reasons, these variables
169 I<must> be written with explicit braces, as C<${^XY}> for example.
170 C<${^XYZ}> is synonymous with ${"\cXYZ"}. Variable names with more
171 than one control character, such as C<${^XY^Z}>, are illegal.
173 The old syntax has not changed. As before, the `^X' may either be a
174 literal control-X character or the two character sequence `caret' plus
175 `X'. When the braces are omitted, the variable name stops after the
176 control character. Thus C<"$^XYZ"> continues to be synonymous with
177 C<$^X . "YZ"> as before.
179 As before, lexical variables may not have names beginning with control
180 characters. As before, variables whose names begin with a control
181 character are always forced to be in package `main'. These variables
182 are all reserved for future extensions, except the ones that begin
183 with C<^_>, which may be used by user programs and will not acquire a
184 special meaning in any future version of Perl.
186 =head1 Significant bug fixes
188 =head2 E<lt>HANDLEE<gt> on empty files
190 With C<$/> set to C<undef>, slurping an empty file returns a string of
191 zero length (instead of C<undef>, as it used to) for the first time the
192 HANDLE is read. Subsequent reads yield C<undef>.
194 This means that the following will append "foo" to an empty file (it used
195 to not do anything before):
197 perl -0777 -pi -e 's/^/foo/' empty_file
199 Note that the behavior of:
201 perl -pi -e 's/^/foo/' empty_file
203 is unchanged (it continues to leave the file empty).
205 =head2 C<eval '...'> improvements
207 Line numbers (as reflected by caller() and most diagnostics) within
208 C<eval '...'> were often incorrect when here documents were involved.
209 This has been corrected.
211 Lexical lookups for variables appearing in C<eval '...'> within
212 functions that were themselves called within an C<eval '...'> were
213 searching the wrong place for lexicals. They now correctly terminate
214 the lexical search at the subroutine call boundary.
216 Parsing of here documents used to be flawed when they appeared as
217 the replacement expression in C<eval 's/.../.../e'>. This has
220 =head1 Supported Platforms
226 VM/ESA is now supported.
230 Siemens BS2000 is now supported under the POSIX Shell.
234 The Mach CThreads (NEXTSTEP, OPENSTEP) are now supported by the Thread
239 GNU/Hurd is now supported.
243 Rhapsody is now supported.
253 IO constants (SEEK_*, _IO*).
257 Directory-related IO methods (new, read, close, rewind, tied delete).
259 =item op/io_multihomed
261 INET sockets with multi-homed hosts.
277 Verify operations that access pad objects (lexicals and temporaries).
281 =head1 Modules and Pragmata
289 Added Dumpvalue module provides screen dumps of Perl data.
293 You can now run tests for I<n> seconds instead of guessing the right
294 number of tests to run.
298 More Fcntl constants added: F_SETLK64, F_SETLKW64, O_LARGEFILE for
299 large (more than 4G) file access (the 64-bit support is not yet
300 working, though, so no need to get overly excited), Free/Net/OpenBSD
301 locking behaviour flags F_FLOCK, F_POSIX, Linux F_SHLCK, and
302 O_ACCMODE: the mask of O_RDONLY, O_WRONLY, and O_RDWR.
306 The accessor methods Re, Im, arg, abs, rho, and theta, can now also
307 act as mutators (accessor $z->Re(), mutator $z->Re(3)).
311 A little bit of radial trigonometry (cylindrical and spherical) added,
312 radial coordinate conversions and the great circle distance.
316 The timelocal() and timegm() functions used to silently return bogus
317 results when the date exceeded the machine's integer range. They
318 consistently croak() if the date falls in an unsupported range.
324 C<use utf8;>, to enable UTF-8 and Unicode support.
326 Lexical warnings pragma, C<use warning;>, to control optional warnings.
328 C<use filetest;>, to control the behaviour of filetests (C<-r> C<-w> ...).
329 Currently only one subpragma implemented, "use filetest 'access';",
330 that enables the use of access(2) or equivalent to check the
331 permissions instead of using stat(2) as usual. This matters
332 in filesystems where there are ACLs (access control lists), the
333 stat(2) might lie, while access(2) knows better.
335 =head1 Utility Changes
339 =head1 Documentation Changes
343 =item perlopentut.pod
345 A tutorial on using open() effectively.
349 A tutorial that introduces the essentials of references.
353 =head1 New Diagnostics
355 =item /%s/: Unrecognized escape \\%c passed through
357 (W) You used a backslash-character combination which is not recognized
358 by Perl. This combination appears in an interpolated variable or a
359 C<'>-delimited regular expression.
361 =item Unrecognized escape \\%c passed through
363 (W) You used a backslash-character combination which is not recognized
366 =item Missing command in piped open
368 (W) You used the C<open(FH, "| command")> or C<open(FH, "command |")>
369 construction, but the command was missing or blank.
371 =head1 Obsolete Diagnostics
375 =head1 Configuration Changes
377 You can use "Configure -Uinstallusrbinperl" which causes installperl
378 to skip installing perl also as /usr/bin/perl. This is useful if you
379 prefer not to modify /usr/bin for some reason or another but harmful
380 because many scripts assume to find Perl in /usr/bin/perl.
382 =head1 Configuration Changes
384 You can use "Configure -Uinstallusrbinperl" which causes installperl
385 to skip installing perl also as /usr/bin/perl. This is useful if you
386 prefer not to modify /usr/bin for some reason or another but harmful
387 because many scripts assume to find Perl in /usr/bin/perl.
391 If you find what you think is a bug, you might check the headers of
392 recently posted articles in the comp.lang.perl.misc newsgroup.
393 There may also be information at http://www.perl.com/perl/, the Perl
396 If you believe you have an unreported bug, please run the B<perlbug>
397 program included with your release. Make sure you trim your bug down
398 to a tiny but sufficient test case. Your bug report, along with the
399 output of C<perl -V>, will be sent off to <F<perlbug@perl.com>> to be
400 analysed by the Perl porting team.
404 The F<Changes> file for exhaustive details on what changed.
406 The F<INSTALL> file for how to build Perl.
408 The F<README> file for general stuff.
410 The F<Artistic> and F<Copying> files for copyright information.
414 Written by Gurusamy Sarathy <F<gsar@umich.edu>>, with many contributions
415 from The Perl Porters.
417 Send omissions or corrections to <F<perlbug@perl.com>>.