make EMBEDMYMALLOC the default and provide PERL_POLLUTE_MALLOC to let
[p5sagit/p5-mst-13.2.git] / pod / perldelta.pod
CommitLineData
ba8251e8 1=head1 NAME
2
e02fdbd2 3perldelta - what's new for perl5.006 (as of 5.005_54)
ba8251e8 4
5=head1 DESCRIPTION
6
7This document describes differences between the 5.005 release and this one.
8
9=head1 Incompatible Changes
10
e02fdbd2 11=head2 Perl Source Incompatibilities
12
13None known at this time.
14
15=head2 C Source Incompatibilities
16
17=over 4
18
19=item C<PERL_POLLUTE>
20
21Release 5.005 grandfathered old global symbol names by providing preprocessor
22macros for extension source compatibility. As of release 5.006, these
23preprocessor definitions are not available by default. You need to explicitly
24compile perl with C<-DPERL_POLLUTE> in order to get these definitions.
25
86058a2d 26=item C<PERL_POLLUTE_MALLOC>
27
28Enabling the use of Perl's malloc in release 5.005 and earlier caused
29the namespace of system versions of the malloc family of functions to
30be usurped by the Perl versions of these functions, since they used the
31same names by default.
32
33Besides causing problems on platforms that do not allow these functions to
34be cleanly replaced, this also meant that the system versions could not
35be called in programs that used Perl's malloc. Previous versions of Perl
36have allowed this behavior to be suppressed with the HIDEMYMALLOC and
37EMBEDMYMALLOC preprocessor definitions.
38
39As of release 5.006, Perl's malloc family of functions have default names
40distinct from the system versions. You need to explicitly compile perl with
41C<-DPERL_POLLUTE_MALLOC> in order to get the older behavior. HIDEMYMALLOC
42and EMBEDMYMALLOC have no effect, since the behavior they enabled is now
43the default.
44
45Note that these functions do B<not> constitute Perl's memory allocation API.
46See L<perlguts/"Memory Allocation"> for further information about that.
47
e02fdbd2 48=item C<PL_na> and C<dTHR> Issues
49
50The C<PL_na> global is now thread local, so a C<dTHR> declaration is needed
51in the scope in which it appears. XSUBs should handle this automatically,
52but if you have used C<PL_na> in support functions, you either need to
53change the C<PL_na> to a local variable (which is recommended), or put in
54a C<dTHR>.
55
56=back
57
58=head2 Binary Incompatibilities
59
60This release is not binary compatible with the 5.005 release and its
61maintenance versions.
62
ba8251e8 63=head1 Core Changes
64
5fdc711f 65=head2 Binary numbers supported
66
4f19785b 67Binary numbers are now supported as literals, in s?printf formats, and
68C<oct()>:
69
70 $answer = 0b101010;
71 printf "The answer is: %b\n", oct("0b101010");
72
5fdc711f 73=head2 syswrite() ease-of-use
74
6c67e1bb 75The length argument of C<syswrite()> is now optional.
76
5fdc711f 77=head2 64-bit support
78
6c67e1bb 79Better 64-bit support -- but full support still a distant goal. One
80must Configure with -Duse64bits to get Configure to probe for the
81extent of 64-bit support. Depending on the platform (hints file) more
82or less 64-awareness becomes available. As of 5.005_54 at least
83somewhat 64-bit aware platforms are HP-UX 11 or better, Solaris 2.6 or
84better, IRIX 6.2 or better. Naturally 64-bit platforms like Digital
85UNIX and UNICOS also have 64-bit support.
e02fdbd2 86
62c18ce2 87=head2 Better syntax checks on parenthesized unary operators
88
89Expressions such as:
90
91 print defined(&foo,&bar,&baz);
92 print uc("foo","bar","baz");
93 undef($foo,&bar);
94
95used to be accidentally allowed in earlier versions, and produced
96unpredictable behavior. Some of them produced ancillary warnings
97when used in this way, while others silently did the wrong thing.
98
99The parenthesized forms of most unary operators that expect a single
100argument will now ensure that they are not called with more than one
101argument, making the above cases syntax errors. Note that the usual
102behavior of:
103
104 print defined &foo, &bar, &baz;
105 print uc "foo", "bar", "baz";
106 undef $foo, &bar;
107
108remains unchanged. See L<perlop>.
109
ba8251e8 110=head1 Supported Platforms
111
5fdc711f 112=over 4
113
114=item *
115
6c67e1bb 116VM/ESA is now supported.
117
5fdc711f 118=item *
119
6c67e1bb 120Siemens BS200 is now supported.
121
5fdc711f 122=item *
123
6c67e1bb 124The Mach CThreads (NeXTstep) are now supported by the Thread extension.
125
5fdc711f 126=back
127
6c67e1bb 128=head1 New tests
129
130=over 4
131
132=item op/io_const
133
134IO constants (SEEK_*, _IO*).
135
136=item op/io_dir
137
138Directory-related IO methods (new, read, close, rewind, tied delete).
139
140=item op/io_multihomed
141
142INET sockets with multi-homed hosts.
143
144=item op/io_poll
145
146IO poll().
147
148=item op/io_unix
149
150UNIX sockets.
151
152=item op/filetest
153
154File test operators.
155
156=item op/lex_assign
157
5fdc711f 158Verify operations that access pad objects (lexicals and temporaries).
6c67e1bb 159
160=back
e02fdbd2 161
ba8251e8 162=head1 Modules and Pragmata
163
3e8c4fa0 164=head2 Modules
165
b7d8191e 166=over 4
167
168=item Dumpvalue
169
170Added Dumpvalue module provides screen dumps of Perl data.
171
172=item Benchmark
173
174You can now run tests for I<x> seconds instead of guessing the right
175number of tests to run.
176
177=item Fcntl
178
179More Fcntl constants added: F_SETLK64, F_SETLKW64, O_LARGEFILE for
180large (more than 4G) file access (the 64-bit support is not yet
181working, though, so no need to get overly excited), Free/Net/OpenBSD
182locking behaviour flags F_FLOCK, F_POSIX, Linux F_SHLCK, and
183O_ACCMODE: the mask of O_RDONLY, O_WRONLY, and O_RDWR.
184
185=item Math::Complex
186
187The accessors methods Re, Im, arg, abs, rho, theta, methods can
188($z->Re()) now also act as mutators ($z->Re(3)).
189
190=item Math::Trig
191
192A little bit of radial trigonometry (cylindrical and spherical) added,
193for example the great circle distance.
194
195=back
3e8c4fa0 196
197=head2 Pragmata
198
6c67e1bb 199Lexical warnings pragma, "use warning;", to control optional warnings.
200
201Filetest pragma, to control the behaviour of filetests (C<-r> C<-w> ...).
202Currently only one subpragma implemented, "use filetest 'access';",
203that enables the use of access(2) or equivalent to check the
204permissions instead of using stat(2) as usual. This matters
205in filesystems where there are ACLs (access control lists), the
206stat(2) might lie, while access(2) knows better.
207
ba8251e8 208=head1 Utility Changes
209
e02fdbd2 210Todo.
211
ba8251e8 212=head1 Documentation Changes
213
5fdc711f 214=over 4
215
216=item perlopentut.pod
f8284313 217
5fdc711f 218A tutorial on using open() effectively.
219
220=item perlreftut.pod
221
222A tutorial that introduces the essentials of references.
223
224=back
e02fdbd2 225
ba8251e8 226=head1 New Diagnostics
227
6b121555 228=item /%s/: Unrecognized escape \\%c passed through
229
230(W) You used a backslash-character combination which is not recognized
231by Perl. This combination appears in an interpolated variable or a
232C<'>-delimited regular expression.
233
234=item Unrecognized escape \\%c passed through
235
236(W) You used a backslash-character combination which is not recognized
237by Perl.
e02fdbd2 238
06eaf0bc 239=item Missing command in piped open
240
241(W) You used the C<open(FH, "| command")> or C<open(FH, "command |")>
242construction, but the command was missing or blank.
243
ba8251e8 244=head1 Obsolete Diagnostics
245
e02fdbd2 246Todo.
247
04d420f9 248=head1 Configuration Changes
249
250You can use "Configure -Uinstallusrbinperl" which causes installperl
251to skip installing perl also as /usr/bin/perl. This is useful if you
252prefer not to modify /usr/bin for some reason or another but harmful
253because many scripts assume to find Perl in /usr/bin/perl.
254
ba8251e8 255=head1 BUGS
256
257If you find what you think is a bug, you might check the headers of
258recently posted articles in the comp.lang.perl.misc newsgroup.
259There may also be information at http://www.perl.com/perl/, the Perl
260Home Page.
261
262If you believe you have an unreported bug, please run the B<perlbug>
263program included with your release. Make sure you trim your bug down
264to a tiny but sufficient test case. Your bug report, along with the
265output of C<perl -V>, will be sent off to <F<perlbug@perl.com>> to be
266analysed by the Perl porting team.
267
268=head1 SEE ALSO
269
270The F<Changes> file for exhaustive details on what changed.
271
272The F<INSTALL> file for how to build Perl.
273
274The F<README> file for general stuff.
275
276The F<Artistic> and F<Copying> files for copyright information.
277
278=head1 HISTORY
279
280Written by Gurusamy Sarathy <F<gsar@umich.edu>>, with many contributions
281from The Perl Porters.
282
283Send omissions or corrections to <F<perlbug@perl.com>>.
284
285=cut