-=head1 How to write a perldelta
+=head1 NAME
+
+how_to_write_a_perldelta - How to write a perldelta
+
+=head2 Description
This is intended as a guide for how to write a perldelta. There has never
been a formal specification - the working rule is "fake up a document that
=encoding utf8
+=head1 NAME
+
+release_schedule - Perl 5 release schedule
+
=head1 STABLE RELEASE SCHEDULE
This schedule lists the projected or historical development and
use vars qw{ $VERSION @EXPORT };
-$VERSION = '0.89';
+$VERSION = '0.90';
use Filter::Util::Call;
use Carp;
Filter::Simple - Simplified source filtering
-
=head1 SYNOPSIS
# in MyFilter.pm:
# use warnings; # dont use warnings for older Perls
use vars qw/$VERSION/;
-$VERSION = '1.998';
+$VERSION = '1.999';
package Math::BigInt;
=head1 METHODS
-=head2 __emu_bxor
+=over
-=head2 __emu_band
+=item __emu_bxor
-=head2 __emu_bior
+=item __emu_band
+
+=item __emu_bior
+
+=back
=head1 LICENSE
@ISA = qw(Math::BigFloat);
-$VERSION = '0.2604';
+$VERSION = '0.2605';
$VERSION = eval $VERSION;
# inherit overload from Math::BigFloat, but disable the bitwise ops that don't
This method was added in v0.20 of Math::BigRat (May 2007).
-See also L</blog()>.
+See also C<blog()>.
=head2 bnok()
use 5.003_11;
use Scalar::Util qw(reftype refaddr);
-$Safe::VERSION = "2.35";
+$Safe::VERSION = "2.36";
# *** Don't declare any lexicals above this point ***
#
in the compartment (I<all> other operators will be permitted, so you probably
don't want to use this method).
-=head2 trap (OP, ...)
-
-=head2 untrap (OP, ...)
+=head2 trap (OP, ...), untrap (OP, ...)
The trap and untrap methods are synonyms for deny and permit
respectfully.
$warning = '';
warn
'Lexing code attempted to stuff non-Latin-1 character into Latin-1 input';
-like $warning, qr/using lex_stuff_pvn or similar/, 'L<foo|bar/baz>';
+like $warning, qr/lex_stuff_pvn or similar/, 'L<foo|bar/baz>';
# Multiple messages with the same description
seek STDERR, 0,0;
=over 4
-=item Z<>B<*> is a wild-card
+=item *
-=item B<(\\d+)> in the info column gives the number of code points matched by
+B<*> is a wild-card
+
+=item *
+
+B<(\\d+)> in the info column gives the number of code points matched by
this property.
-=item B<$DEPRECATED> means this is deprecated.
+=item *
+
+B<$DEPRECATED> means this is deprecated.
+
+=item *
+
+B<$OBSOLETE> means this is obsolete.
+
+=item *
+
+B<$STABILIZED> means this is stabilized.
-=item B<$OBSOLETE> means this is obsolete.
+=item *
-=item B<$STABILIZED> means this is stabilized.
+B<$STRICTER> means tighter (stricter) name matching applies.
-=item B<$STRICTER> means tighter (stricter) name matching applies.
+=item *
-=item B<$DISCOURAGED> means use of this form is discouraged, and may not be
+B<$DISCOURAGED> means use of this form is discouraged, and may not be
stable.
=back
Constructs, checks, and returns an op of any type that involves an
embedded C-level pointer (PV). I<type> is the opcode. I<flags> gives
the eight bits of C<op_flags>. I<pv> supplies the C-level pointer, which
-must have been allocated using L</PerlMemShared_malloc>; the memory will
+must have been allocated using C<PerlMemShared_malloc>; the memory will
be freed when the op is destroyed.
=cut
Constructs a state op (COP). The state op is normally a C<nextstate> op,
but will be a C<dbstate> op if debugging is enabled for currently-compiled
-code. The state op is populated from L</PL_curcop> (or L</PL_compiling>).
+code. The state op is populated from C<PL_curcop> (or C<PL_compiling>).
If I<label> is non-null, it supplies the name of a label to attach to
the state op; this function takes ownership of the memory pointed at by
I<label>, and will free it. I<flags> gives the eight bits of C<op_flags>
(F) The end of the perl code contained within the {...} must be
followed immediately by a ')'.
-=item Z<>500 Server error
-
-See Server error.
-
-=item Server error
+=item Server error (a.k.a. "500 Server error")
(A) This is the error message generally seen in a browser window
when trying to run a CGI program (including SSI) over the web. The
The C<POSIX::getattr> function can do this more portably on
systems purporting POSIX compliance. See also the C<Term::ReadKey>
-module from your nearest CPAN site; details on CPAN can be found under
-L<perlmodlib/CPAN>.
+module from your nearest L<CPAN|http://www.cpan.org> site.
=item getlogin
X<getlogin> X<login>
=head2 Why do regex character classes sometimes match only in the ASCII range?
-=head2 Why do some characters not uppercase or lowercase correctly?
-
Starting in Perl 5.14 (and partially in Perl 5.12), just put a
C<use feature 'unicode_strings'> near the beginning of your program.
Within its lexical scope you shouldn't have this problem. It also is
For a more detailed discussion, see L<Unicode::Semantics> on CPAN.
+=head2 Why do some characters not uppercase or lowercase correctly?
+
+See the answer to the previous question.
+
=head2 How can I determine if a string is a text string or a binary string?
You can't. Some use the UTF8 flag for this, but that's misuse, and makes well
YAML
YAML::Syck
YAML::Tiny
-dist/filter-simple/lib/filter/simple.pm Verbatim paragraph in NAME section 1
-dist/locale-maketext/lib/locale/maketext/tpj13.pod No items in =over / =back list 3
-dist/math-bigint/lib/math/bigint/calcemu.pm empty section in previous paragraph 3
-dist/math-bigrat/lib/math/bigrat.pm unresolved internal link 1
dist/net-ping/lib/net/ping.pm Verbatim line length including indents exceeds 100 by 1
-dist/safe/safe.pm empty section in previous paragraph 1
-ext/pod-html/bin/pod2html Pod NAME already used 1
ext/posix/lib/posix.pod Verbatim line length including indents exceeds 100 by 2
-pod/perlapi.pod unresolved internal link 3
pod/perlbook.pod Verbatim line length including indents exceeds 100 by 1
pod/perldebguts.pod Verbatim line length including indents exceeds 100 by 2
-pod/perldiag.pod =item type mismatch 1
pod/perldtrace.pod Verbatim line length including indents exceeds 100 by 4
pod/perlebcdic.pod Verbatim line length including indents exceeds 100 by 10
-pod/perlfunc.pod There is more than one target 1
pod/perlmacosx.pod Verbatim line length including indents exceeds 100 by 3
pod/perlos2.pod Verbatim line length including indents exceeds 100 by 4
pod/perlperf.pod Verbatim line length including indents exceeds 100 by 32
pod/perlrun.pod Verbatim line length including indents exceeds 100 by 1
pod/perlthrtut.pod Verbatim line length including indents exceeds 100 by 1
pod/perltru64.pod Verbatim line length including indents exceeds 100 by 1
-pod/perlunifaq.pod empty section in previous paragraph 1
-pod/perluniprops.pod =item type mismatch 6
pod/perlwin32.pod Verbatim line length including indents exceeds 100 by 6
-porting/how_to_write_a_perldelta.pod There is no NAME 1
porting/release_managers_guide.pod Verbatim line length including indents exceeds 100 by 1
-porting/release_schedule.pod There is no NAME 1
-utils/pod2html Pod NAME already used 1
-x2p/a2p.pod empty section in previous paragraph 2
lib/benchmark.pm Verbatim line length including indents exceeds 100 by 2
-lib/config.pod nested commands F<...F<...>...> 3
Larry Wall E<lt>F<larry@wall.org>E<gt>
-=head1 FILES
-
=head1 SEE ALSO
perl The perl compiler/interpreter
s2p sed to perl translator
-=head1 DIAGNOSTICS
-
=head1 BUGS
It would be possible to emulate awk's behavior in selecting string