=item 11656
-allow builing perl with -DUSE_UTF8_SCRIPTS which makes UTF-8
+allow building perl with -DUSE_UTF8_SCRIPTS which makes UTF-8
the default script encoding (not the default since that would
break all scripts having legacy eight-bit data in them)
=item *
Malformed Unicode encodings (UTF-8 and UTF-16) cause a lot of warnings,
-ad doestrying to use UTF-16 surrogates (which are unimplemented).
+as does trying to use UTF-16 surrogates (which are unimplemented).
=item *
=head2 Assertions
-Perl 5.9.0 has experimental support for assertions. Note that hhe user
+Perl 5.9.0 has experimental support for assertions. Note that the user
interface is not fully stabilized yet, and it may change until the 5.10.0
release. A new command-line switch, B<-A>, is used to activate
assertions, which are declared with the C<assertions> pragma. See
=head1 DESCRIPTION
This document describes differences between the 5.9.0 and the 5.9.1
-developement releases. See L<perl590delta> for the differences between
+development releases. See L<perl590delta> for the differences between
5.8.0 and 5.9.0.
=head1 Incompatible Changes
The lvalues returned by the three argument form of substr() used to be a
"fixed length window" on the original string. In some cases this could
cause surprising action at distance or other undefined behaviour. Now the
-length of the window adjusts iself to the length of the string assigned to
+length of the window adjusts itself to the length of the string assigned to
it.
=head2 The C<:unique> attribute is only meaningful for globals
=head1 DESCRIPTION
This document describes differences between the 5.9.1 and the 5.9.2
-developement releases. See L<perl590delta> and L<perl591delta> for the
+development releases. See L<perl590delta> and L<perl591delta> for the
differences between 5.8.0 and 5.9.1.
=head1 Incompatible Changes
marked as readonly and the key is subsequently deleted, the key is not actually
deleted but is marked by assigning it a value of &PL_sv_placeholder. This tags
it so it will be ignored by future operations such as iterating over the hash,
-but will still allow the hash to have a value reaasigned to the key at some
+but will still allow the hash to have a value reassigned to the key at some
future point. This function clears any such placeholder keys from the hash.
See Hash::Util::lock_keys() for an example of its use.
in there (they will point at the beginning of the I<next> character).
If the pointers behind pe1 or pe2 are non-NULL, they are the end
pointers beyond which scanning will not continue under any
-circustances. If the byte lengths l1 and l2 are non-zero, s1+l1 and
+circumstances. If the byte lengths l1 and l2 are non-zero, s1+l1 and
s2+l2 will be used as goal end pointers that will also stop the scan,
and which qualify towards defining a successful match: all the scans
that define an explicit length must reach their goal pointers for
This corresponds to fflush(). Sends any buffered write data to the
underlying file. If called with C<NULL> this may flush all open
-streams (or core dump with some USE_STDIO implementattions). Calling
+streams (or core dump with some USE_STDIO implementations). Calling
on a handle open for read only, or on which last operation was a read
of some kind may lead to undefined behaviour on some USE_STDIO
implementations. The USE_PERLIO (layers) implementation tries to
=head2 Subscripts
-An array is subscripted by specifying a dollary sign (C<$>), then the
+An array is subscripted by specifying a dollar sign (C<$>), then the
name of the array (without the leading C<@>), then the subscript inside
square brackets. For example:
- just about whatever you throw at it:
Let's make a quick object and x-plode it, first we'll start the debugger:
-it wants some form of input from STDIN, so we give it something non-commital,
+it wants some form of input from STDIN, so we give it something non-committal,
a zero:
> perl -de 0
"loop". In future Perl's signal mechanism may be changed to avoid this
- perhaps by simply disallowing %SIG handlers on signals of that
type. Until then the work-round is not to set a %SIG handler on those
-signals. (Which signals they are is operating system dependant.)
+signals. (Which signals they are is operating system dependent.)
=item Signals triggered by operating system state
What C<\n> represents depends on the type of file opened. It usually
represents C<\012> but it could also be C<\015>, C<\012>, C<\015\012>,
-C<\000>, C<\040>, or nothing depending on the file organiztion and
+C<\000>, C<\040>, or nothing depending on the file organization and
record format. The VMS::Stdio module provides access to the
special fopen() requirements of files with unusual attributes on VMS.
literally. If Unicode is in effect, C<\s> matches also "\x{85}",
"\x{2028}, and "\x{2029}", see L<perlunicode> for more details about
C<\pP>, C<\PP>, and C<\X>, and L<perluniintro> about Unicode in general.
-You can define your own C<\p> and C<\P> propreties, see L<perlunicode>.
+You can define your own C<\p> and C<\P> properties, see L<perlunicode>.
The POSIX character class syntax
Inside the C<(?{...})> block, C<$_> refers to the string the regular
expression is matching against. You can also use C<pos()> to know what is
-the current position of matching withing this string.
+the current position of matching within this string.
The C<code> is properly scoped in the following sense: If the assertion
is backtracked (compare L<"Backtracking">), all changes introduced after
character class of Unicode 'marks', for example accent marks.
For the full list see L<perlunicode>.
-The Unicode has also been separated into various sets of charaters
+The Unicode has also been separated into various sets of characters
which you can test with C<\p{In...}> (in) and C<\P{In...}> (not in),
for example C<\p{Latin}>, C<\p{Greek}>, or C<\P{Katakana}>.
For the full list see L<perlunicode>.
$pat = qr/(?{ $foo = 1 })/; # precompile code regexp
/foo${pat}bar/; # compiles ok
-If a regexp has (1) code expressions and interpolating variables,or
+If a regexp has (1) code expressions and interpolating variables, or
(2) a variable that interpolates a code expression, perl treats the
regexp as an error. If the code expression is precompiled into a
variable, however, interpolating is ok. The question is, why is this
lines printed. If a file named by an argument cannot be opened for
some reason, Perl warns you about it and moves on to the next file.
-Here is an efficient way to delete all files that haven't been modifed for
+Here is an efficient way to delete all files that haven't been modified for
at least a week:
find . -mtime +7 -print | perl -nle unlink
The C<BEGIN>, C<CHECK>, C<INIT> and C<END> subroutines are not so much
subroutines as named special code blocks, of which you can have more
-than one in a package, and which you can B<not> call explicitely. See
+than one in a package, and which you can B<not> call explicitly. See
L<perlmod/"BEGIN, CHECK, INIT and END">
=head2 Private Variables via my()
=head2 Semaphores: Synchronizing Data Access
Semaphores are a kind of generic locking mechanism. In their most basic
-form, they behave very much like lockable scalars, except that thay
+form, they behave very much like lockable scalars, except that they
can't hold data, and that they must be explicitly unlocked. In their
advanced form, they act like a kind of counter, and can allow multiple
threads to have the 'lock' at any one time.
defines one local patch, of the form "MAINT12345" or "RC1". The output of
perl -v doesn't report that a perl isn't an official release, and this
information can get lost in bugs reports. Because of this, the minor version
-isn't bumped up util RC time, to minimise the possibility of versions of perl
+isn't bumped up until RC time, to minimise the possibility of versions of perl
escaping that believe themselves to be newer than they actually are.
It would be useful to find an elegant way to have the "this is an interim
It is widely perceived, and indeed has often been written, that Perl
provides no data hiding, that it affords the class designer no privacy
-nor isolation, merely a rag-tag assortment of weak and unenforcible
+nor isolation, merely a rag-tag assortment of weak and unenforceable
social conventions instead. This perception is demonstrably false and
easily disproven. In the next section, we show how to implement forms
of privacy that are far stronger than those provided in nearly any
properly designed accessor methods is probably not a good idea after all.
Restricting access to class attributes from the class itself is usually
-not enforcible even in strongly object-oriented languages. But in Perl,
+not enforceable even in strongly object-oriented languages. But in Perl,
you can.
Here's one way:
or the AutoLoader, because they alter the lexical scope in which the
module's methods wind up getting compiled.
-The usual mealy-mouthed package-mungeing doubtless applies to setting
+The usual mealy-mouthed package-munging doubtless applies to setting
up names of object attributes. For example, C<< $self->{ObData1} >>
should probably be C<< $self->{ __PACKAGE__ . "_ObData1" } >>, but that
would just confuse the examples.
projects / p5sagit/p5-mst-13.2.git / commitdiff