#endif /* PERL_GLOBAL_STRUCT */
-#ifdef PERL_POLLUTE /* disabled by default in 5.006 */
+#ifdef PERL_POLLUTE /* disabled by default in 5.6.0 */
END
#endif /* PERL_GLOBAL_STRUCT */
-#ifdef PERL_POLLUTE /* disabled by default in 5.006 */
+#ifdef PERL_POLLUTE /* disabled by default in 5.6.0 */
#define DBsingle PL_DBsingle
#define DBsub PL_DBsub
# intending to replace /usr/bin/perl (at least just yet).
# This change makes linux consistent with most other unix platforms
# in having a default of prefix=/usr/local.
-# These notes can probably safely be removed in 5.006_50 and beyond.
+# These notes can probably safely be removed in 5.005_50 and beyond.
#
# 9 April 1999 Andy Dougherty <doughera@lafayette.edu>
#
the language.
If you build a version of the Perl interpreter with C<-DDEBUGGING>,
-Perl's B<-D> commandline flag will cause copious debugging information
+Perl's B<-D> command line flag will cause copious debugging information
to be emitted (see the C<perlrun> manpage). If you build a version of
Perl with compiler debugging information (e.g. with the C compiler's
C<-g> option instead of C<-O>) then you can step through the execution
integers, as it does when native floating point numbers are involved.
The only implication of the term "native" on integers is that the limits for
the maximal and the minimal supported true integral quantities are close to
-powers of 2. However, for "native" floats have a most fundamental
+powers of 2. However, "native" floats have a most fundamental
restriction: they may represent only those numbers which have a relatively
"short" representation when converted to a binary fraction. For example,
0.9 cannot be respresented by a native float, since the binary fraction
=head2 Ignoring A Thread
-join() does three things:it waits for a thread to exit, cleans up
+join() does three things: it waits for a thread to exit, cleans up
after it, and returns any data the thread may have produced. But what
if you're not interested in the thread's return values, and you don't
really care when the thread finishes? All you want is for the thread
Perl's scoping rules don't change because you're using threads. If a
subroutine (or block, in the case of async()) could see a variable if
you weren't running with threads, it can see it if you are. This is
-especially important for the subroutines that create, and makes my
+especially important for the subroutines that create, and makes C<my>
variables even more important. Remember--if your variables aren't
-lexically scoped (declared with C<my>) you're probably sharing it between
-threads.
+lexically scoped (declared with C<my>) you're probably sharing them
+between threads.
=head2 Thread Pitfall: Races
=head1 REVISION
This document was last revised on 13-Oct-1998, for Perl 5.004, 5.005, and
-5.006.
+5.6.0.
=cut