Exporter::Heavy - Exporter guts
-=head1 SYNOPIS
+=head1 SYNOPSIS
(internal use only)
=head1 NAME
- sample - Using GetOpt::Long and Pod::Usage
+ sample - Using Getopt::Long and Pod::Usage
=head1 SYNOPSIS
=head1 NAME
- sample - Using GetOpt::Long and Pod::Usage
+ sample - Using Getopt::Long and Pod::Usage
=head1 SYNOPSIS
L<perlrun>
L<re>,
and
-L<Devel::Dprof>.
+L<Devel::DProf>.
L<perldebguts>,
L<re>,
L<DB>,
-L<Devel::Dprof>,
+L<Devel::DProf>,
L<dprofpp>,
L<Dumpvalue>,
and
=head2 How can I use a reference as a hash key?
-You can't do this directly, but you could use the standard Tie::Refhash
+You can't do this directly, but you could use the standard Tie::RefHash
module distributed with Perl.
=head1 Data: Misc
=head2 How do I keep persistent data across program calls?
For some specific applications, you can use one of the DBM modules.
-See L<AnyDBM_File>. More generically, you should consult the FreezeThaw,
-Storable, or Class::Eroot modules from CPAN. Starting from Perl 5.8
-Storable is part of the standard distribution. Here's one example using
-Storable's C<store> and C<retrieve> functions:
+See L<AnyDBM_File>. More generically, you should consult the FreezeThaw
+or Storable modules from CPAN. Starting from Perl 5.8 Storable is part
+of the standard distribution. Here's one example using Storable's C<store>
+and C<retrieve> functions:
use Storable;
store(\%hash, "filename");
Starting from Perl 5.6 Perl has had some level of multibyte character
support. Perl 5.8 or later is recommended. Supported multibyte
-character repetoires include Unicode, and legacy encodings
+character repertoires include Unicode, and legacy encodings
through the Encode module. See L<perluniintro>, L<perlunicode>,
and L<Encode>.
=item send SOCKET,MSG,FLAGS
-Sends a message on a socket. Attemps to send the scalar MSG to the
+Sends a message on a socket. Attempts to send the scalar MSG to the
SOCKET filehandle. Takes the same flags as the system call of the
same name. On unconnected sockets you must specify a destination to
send TO, in which case it does a C C<sendto>. Returns the number of
shown in parentheses, and the values of C<SvCUR> and C<SvLEN> reflect
the fake beginning, not the real one.
-Something similar to the offset hack is perfomed on AVs to enable
+Something similar to the offset hack is performed on AVs to enable
efficient shifting and splicing off the beginning of the array; while
C<AvARRAY> points to the first element in the array that is visible from
Perl, C<AvALLOC> points to the real start of the C array. These are
to each key (in C<$_>) it adds the C<=> separator and the hash entry value.
Each triplet is packed with the template code sequence C<A*A*Z*> that
is multiplied with the number of keys. (Yes, that's what the C<keys>
-function resturns in scalar context.) To get the very last null byte,
+function returns in scalar context.) To get the very last null byte,
we add a C<0> at the end of the C<pack> list, to be packed with C<C>.
(Attentive readers may have noticed that we could have omitted the 0.)
prototype (such as C<system> or C<chomp>). If you override them you won't
be able to fully mimic their original syntax.
-The built-ins C<do>, C<require> and C<glob> can also be overriden, but due
+The built-ins C<do>, C<require> and C<glob> can also be overridden, but due
to special magic, their original syntax is preserved, and you don't have
to define a prototype for their replacements. (You can't override the
C<do BLOCK> syntax, though).
the argument C<"Foo/Bar.pm"> in @_. See L<perlfunc/require>.
And, as you'll have noticed from the previous example, if you override
-C<glob>, the C<E<lt>*E<gt>> glob operator is overriden as well.
+C<glob>, the C<E<lt>*E<gt>> glob operator is overridden as well.
-Finally, some built-ins (e.g. C<exists> or C<grep>) can't be overriden.
+Finally, some built-ins (e.g. C<exists> or C<grep>) can't be overridden.
=head2 Autoloading
=head2 IPv6 Support
-There are non-core modules, such as C<Net::IPv6>, but these will need
+There are non-core modules, such as C<Socket6>, but these will need
integrating when IPv6 actually starts to really happen. See RFC 2292
and RFC 2553.
=head2 Replace pod2html with something using Pod::Parser
-The CPAN module C<Malik::Pod::Html> may be a more suitable basis for a
+The CPAN module C<Marek::Pod::Html> may be a more suitable basis for a
C<pod2html> convertor; the current one duplicates the functionality
abstracted in C<Pod::Parser>, which makes updating the POD language
difficult.
leading bits of the start byte tells how many bytes the are in the
encoded character.
-=item UTF-EBDIC
+=item UTF-EBCDIC
-Like UTF-8, but EBDCIC-safe, as UTF-8 is ASCII-safe.
+Like UTF-8, but EBCDIC-safe, as UTF-8 is ASCII-safe.
=item UTF-16, UTF-16BE, UTF16-LE, Surrogates, and BOMs (Byte Order Marks)
=item L<dprofpp|dprofpp>
-Perl comes with a profiler, the F<Devel::Dprof> module. The
+Perl comes with a profiler, the F<Devel::DProf> module. The
F<dprofpp> utility analyzes the output of this profiler and tells you
-which subroutines are taking up the most run time. See L<Devel::Dprof>
+which subroutines are taking up the most run time. See L<Devel::DProf>
for more information.
=item L<perlcc|perlcc>
L<roffitall|roffitall>, L<a2p|a2p>, L<s2p|s2p>, L<find2perl|find2perl>,
L<File::Find|File::Find>, L<pl2pm|pl2pm>, L<perlbug|perlbug>,
L<h2ph|h2ph>, L<c2ph|c2ph>, L<h2xs|h2xs>, L<dprofpp|dprofpp>,
-L<Devel::Dprof>, L<perlcc|perlcc>
+L<Devel::DProf>, L<perlcc|perlcc>
=cut
It is therefore strongly recommended that these macros be used by all
XS modules that make use of static data.
-The easiest way to get a template set of macros to use is by specifiying
+The easiest way to get a template set of macros to use is by specifying
the C<-g> (C<--global>) option with h2xs (see L<h2xs>).
Below is an example module that makes use of the macros.
projects / p5sagit/p5-mst-13.2.git / commitdiff