EcchiShell v1.0

, even when used for other purposes than their built-in ones. If you have a package called C, C, or C, then you can't use the qualified form of an identifier because it would be instead interpreted as a pattern match, a substitution, or a transliteration. X Variables beginning with underscore used to be forced into package main, but we decided it was more useful for package writers to be able to use leading underscore to indicate private variables and method names. However, variables and functions named with a single C<_>, such as $_ and C_{, are still forced into the package C. See also
L.

Ced strings are compiled in the package in which the eval() was
compiled. (Assignments to C<$SIG{}>, however, assume the signal
handler specified is in the C package. Qualify the signal handler
name if you wish to have a signal handler in a package.) For an
example, examine F in the Perl library. It initially switches
to the C package so that the debugger doesn't interfere with variables
in the program you are trying to debug. At various points, however, it
temporarily switches back to the C package to evaluate various
expressions in the context of the C package (or wherever you came
from). See L.

The special symbol C<__PACKAGE__> contains the current package, but cannot
(easily) be used to construct variable names.

See L for other scoping issues related to my() and local(),
and L regarding closures.

=head2 Symbol Tables
X X X<%::> X<%main::> X X X

The symbol table for a package happens to be stored in the hash of that
name with two colons appended. The main symbol table's name is thus
C<%main::>, or C<%::> for short. Likewise the symbol table for the nested
package mentioned earlier is named C<%OUTER::INNER::>.

The value in each entry of the hash is what you are referring to when you
use the C<*name> typeglob notation.

local *main::foo = *main::bar;

You can use this to print out all the variables in a package, for
instance. The standard but antiquated F library and
the CPAN module Devel::Symdump make use of this.

The results of creating new symbol table entries directly or modifying any
entries that are not already typeglobs are undefined and subject to change
between releases of perl.

Assignment to a typeglob performs an aliasing operation, i.e.,

*dick = *richard;

causes variables, subroutines, formats, and file and directory handles
accessible via the identifier C also to be accessible via the
identifier C. If you want to alias only a particular variable or
subroutine, assign a reference instead:

*dick = \$richard;

Which makes $richard and $dick the same variable, but leaves
@richard and @dick as separate arrays. Tricky, eh?

There is one subtle difference between the following statements:

*foo = *bar;
*foo = \$bar;

C<*foo = *bar> makes the typeglobs themselves synonymous while
C<*foo = \$bar> makes the SCALAR portions of two distinct typeglobs
refer to the same scalar value. This means that the following code:

$bar = 1;
*foo = \$bar; # Make $foo an alias for $bar

{
local $bar = 2; # Restrict changes to block
print $foo; # Prints '1'!
}

Would print '1', because C<$foo> holds a reference to the I
C<$bar>. The one that was stuffed away by C and which will be
restored when the block ends. Because variables are accessed through the
typeglob, you can use C<*foo = *bar> to create an alias which can be
localized. (But be aware that this means you can't have a separate
C<@foo> and C<@bar>, etc.)

What makes all of this important is that the Exporter module uses glob
aliasing as the import/export mechanism. Whether or not you can properly
localize a variable that has been exported from a module depends on how
it was exported:

@EXPORT = qw($FOO); # Usual form, can't be localized
@EXPORT = qw(*FOO); # Can be localized

You can work around the first case by using the fully qualified name
(C<$Package::FOO>) where you need a local value, or by overriding it
by saying C<*FOO = *Package::FOO> in your script.

The C<*x = \$y> mechanism may be used to pass and return cheap references
into or from subroutines if you don't want to copy the whole
thing. It only works when assigning to dynamic variables, not
lexicals.

%some_hash = (); # can't be my()
*some_hash = fn( \%another_hash );
sub fn {
local *hashsym = shift;
# now use %hashsym normally, and you
# will affect the caller's %another_hash
my %nhash = (); # do what you want
return \%nhash;
}

On return, the reference will overwrite the hash slot in the
symbol table specified by the *some_hash typeglob. This
is a somewhat tricky way of passing around references cheaply
when you don't want to have to remember to dereference variables
explicitly.

Another use of symbol tables is for making "constant" scalars.
X X

*PI = \3.14159265358979;

Now you cannot alter C<$PI>, which is probably a good thing all in all.
This isn't the same as a constant subroutine, which is subject to
optimization at compile-time. A constant subroutine is one prototyped
to take no arguments and to return a constant expression. See
L for details on these. The C pragma is a
convenient shorthand for these.

You can say C<*foo{PACKAGE}> and C<*foo{NAME}> to find out what name and
package the *foo symbol table entry comes from. This may be useful
in a subroutine that gets passed typeglobs as arguments:

sub identify_typeglob {
my $glob = shift;
print 'You gave me ', *{$glob}{PACKAGE}, '::', *{$glob}{NAME}, "\n";
}
identify_typeglob *foo;
identify_typeglob *bar::baz;

This prints

You gave me main::foo
You gave me bar::baz

The C<*foo{THING}> notation can also be used to obtain references to the
individual elements of *foo. See L.

Subroutine definitions (and declarations, for that matter) need
not necessarily be situated in the package whose symbol table they
occupy. You can define a subroutine outside its package by
explicitly qualifying the name of the subroutine:

package main;
sub Some_package::foo { ... } # &foo defined in Some_package

This is just a shorthand for a typeglob assignment at compile time:

BEGIN { *Some_package::foo = sub { ... } }

and is I the same as writing:

{
package Some_package;
sub foo { ... }
}

In the first two versions, the body of the subroutine is
lexically in the main package, I in Some_package. So
something like this:

package main;

$Some_package::name = "fred";
$main::name = "barney";

sub Some_package::foo {
print "in ", __PACKAGE__, ": \$name is '$name'\n";
}

Some_package::foo();

prints:

in main: $name is 'barney'

rather than:

in Some_package: $name is 'fred'

This also has implications for the use of the SUPER:: qualifier
(see L).

=head2 BEGIN, UNITCHECK, CHECK, INIT and END
X X X X X

Five specially named code blocks are executed at the beginning and at
the end of a running Perl program. These are the C,
C, C, C, and C blocks.

These code blocks can be prefixed with C_{to give the appearance of a
subroutine (although this is not considered good style). One should note
that these code blocks don't really exist as named subroutines (despite
their appearance). The thing that gives this away is the fact that you can
have B of these code blocks in a program, and they will get
B executed at the appropriate moment. So you can't execute any of
these code blocks by name.

A C code block is executed as soon as possible, that is, the moment
it is completely defined, even before the rest of the containing file (or
string) is parsed. You may have multiple C blocks within a file (or
eval'ed string); they will execute in order of definition. Because a C
code block executes immediately, it can pull in definitions of subroutines
and such from other files in time to be visible to the rest of the compile
and run time. Once a C has run, it is immediately undefined and any
code it used is returned to Perl's memory pool.

An C code block is executed as late as possible, that is, after
perl has finished running the program and just before the interpreter
is being exited, even if it is exiting as a result of a die() function.
(But not if it's morphing into another program via C, or
being blown out of the water by a signal--you have to trap that yourself
(if you can).) You may have multiple C blocks within a file--they
will execute in reverse order of definition; that is: last in, first
out (LIFO). C blocks are not executed when you run perl with the
C<-c> switch, or if compilation fails.

Note that C code blocks are B executed at the end of a string
C: if any C code blocks are created in a string C,
they will be executed just as any other C code block of that package
in LIFO order just before the interpreter is being exited.

Inside an C code block, C<$?> contains the value that the program is
going to pass to C. You can modify C<$?> to change the exit
value of the program. Beware of changing C<$?> by accident (e.g. by
running something via C).
X<$?>

Inside of a C block, the value of C<${^GLOBAL_PHASE}> will be
C<"END">.

C, C and C code blocks are useful to catch the
transition between the compilation phase and the execution phase of
the main program.

C blocks are run just after the unit which defined them has
been compiled. The main program file and each module it loads are
compilation units, as are string Cs, code compiled using the
C<(?{ })> construct in a regex, calls to C, C,
and code after the C<-e> switch on the command line.

C and C blocks are not directly related to the phase of
the interpreter. They can be created and executed during any phase.

C code blocks are run just after the B Perl compile phase ends
and before the run time begins, in LIFO order. C code blocks are used
in the Perl compiler suite to save the compiled state of the program.

Inside of a C block, the value of C<${^GLOBAL_PHASE}> will be
C<"CHECK">.

C blocks are run just before the Perl runtime begins execution, in
"first in, first out" (FIFO) order.

Inside of an C block, the value of C<${^GLOBAL_PHASE}> will be C<"INIT">.

The C and C blocks in code compiled by C, string C,
or string C will not be executed if they occur after the end of the
main compilation phase; that can be a problem in mod_perl and other persistent
environments which use those functions to load code at runtime.

When you use the B<-n> and B<-p> switches to Perl, C and
C work just as they do in B, as a degenerate case.
Both C and C blocks are run when you use the B<-c>
switch for a compile-only syntax check, although your main code
is not.

The B program makes it all clear, eventually:

#!/usr/bin/perl

# begincheck

print "10. Ordinary code runs at runtime.\n";

END { print "16. So this is the end of the tale.\n" }
INIT { print " 7. INIT blocks run FIFO just before runtime.\n" }
UNITCHECK {
print " 4. And therefore before any CHECK blocks.\n"
}
CHECK { print " 6. So this is the sixth line.\n" }

print "11. It runs in order, of course.\n";

BEGIN { print " 1. BEGIN blocks run FIFO during compilation.\n" }
END { print "15. Read perlmod for the rest of the story.\n" }
CHECK { print " 5. CHECK blocks run LIFO after all compilation.\n" }
INIT { print " 8. Run this again, using Perl's -c switch.\n" }

print "12. This is anti-obfuscated code.\n";

END { print "14. END blocks run LIFO at quitting time.\n" }
BEGIN { print " 2. So this line comes out second.\n" }
UNITCHECK {
print " 3. UNITCHECK blocks run LIFO after each file is compiled.\n"
}
INIT { print " 9. You'll see the difference right away.\n" }

print "13. It merely _looks_ like it should be confusing.\n";

__END__

=head2 Perl Classes
X X<@ISA>

There is no special class syntax in Perl, but a package may act
as a class if it provides subroutines to act as methods. Such a
package may also derive some of its methods from another class (package)
by listing the other package name(s) in its global @ISA array (which
must be a package global, not a lexical).

For more on this, see L and L.

=head2 Perl Modules
X

A module is just a set of related functions in a library file, i.e.,
a Perl package with the same name as the file. It is specifically
designed to be reusable by other modules or programs. It may do this
by providing a mechanism for exporting some of its symbols into the
symbol table of any package using it, or it may function as a class
definition and make its semantics available implicitly through
method calls on the class and its objects, without explicitly
exporting anything. Or it can do a little of both.

For example, to start a traditional, non-OO module called Some::Module,
create a file called F and start with this template:

package Some::Module; # assumes Some/Module.pm

use strict;
use warnings;

BEGIN {
require Exporter;

# set the version for version checking
our $VERSION = 1.00;

# Inherit from Exporter to export functions and variables
our @ISA = qw(Exporter);

# Functions and variables which are exported by default
our @EXPORT = qw(func1 func2);

# Functions and variables which can be optionally exported
our @EXPORT_OK = qw($Var1 %Hashit func3);
}

# exported package globals go here
our $Var1 = '';
our %Hashit = ();

# non-exported package globals go here
# (they are still accessible as $Some::Module::stuff)
our @more = ();
our $stuff = '';

# file-private lexicals go here, before any functions which use them
my $priv_var = '';
my %secret_hash = ();

# here's a file-private function as a closure,
# callable as $priv_func->();
my $priv_func = sub {
...
};

# make all your functions, whether exported or not;
# remember to put something interesting in the {} stubs
sub func1 { ... }
sub func2 { ... }

# this one isn't exported, but could be called directly
# as Some::Module::func3()
sub func3 { ... }

END { ... } # module clean-up code here (global destructor)

1; # don't forget to return a true value from the file

Then go on to declare and use your variables in functions without
any qualifications. See L and the L for
details on mechanics and style issues in module creation.

Perl modules are included into your program by saying

use Module;

or

use Module LIST;

This is exactly equivalent to

BEGIN { require 'Module.pm'; 'Module'->import; }

or

BEGIN { require 'Module.pm'; 'Module'->import( LIST ); }

As a special case

use Module ();

is exactly equivalent to

BEGIN { require 'Module.pm'; }

All Perl module files have the extension F<.pm>. The C operator
assumes this so you don't have to spell out "F" in quotes.
This also helps to differentiate new modules from old F<.pl> and
F<.ph> files. Module names are also capitalized unless they're
functioning as pragmas; pragmas are in effect compiler directives,
and are sometimes called "pragmatic modules" (or even "pragmata"
if you're a classicist).

The two statements:

require SomeModule;
require "SomeModule.pm";

differ from each other in two ways. In the first case, any double
colons in the module name, such as C, are translated
into your system's directory separator, usually "/". The second
case does not, and would have to be specified literally. The other
difference is that seeing the first C clues in the compiler
that uses of indirect object notation involving "SomeModule", as
in C<$ob = purge SomeModule>, are method calls, not function calls.
(Yes, this really can make a difference.)

Because the C statement implies a C block, the importing
of semantics happens as soon as the C statement is compiled,
before the rest of the file is compiled. This is how it is able
to function as a pragma mechanism, and also how modules are able to
declare subroutines that are then visible as list or unary operators for
the rest of the current file. This will not work if you use C
instead of C. With C you can get into this problem:

require Cwd; # make Cwd:: accessible
$here = Cwd::getcwd();

use Cwd; # import names from Cwd::
$here = getcwd();

require Cwd; # make Cwd:: accessible
$here = getcwd(); # oops! no main::getcwd()

In general, C is recommended over C,
because it determines module availability at compile time, not in the
middle of your program's execution. An exception would be if two modules
each tried to C each other, and each also called a function from
that other module. In that case, it's easy to use C instead.

Perl packages may be nested inside other package names, so we can have
package names containing C<::>. But if we used that package name
directly as a filename it would make for unwieldy or impossible
filenames on some systems. Therefore, if a module's name is, say,
C, then its definition is actually found in the library
file F.

Perl modules always have a F<.pm> file, but there may also be
dynamically linked executables (often ending in F<.so>) or autoloaded
subroutine definitions (often ending in F<.al>) associated with the
module. If so, these will be entirely transparent to the user of
the module. It is the responsibility of the F<.pm> file to load
(or arrange to autoload) any additional functionality. For example,
although the POSIX module happens to do both dynamic loading and
autoloading, the user can say just C to get it all.

=head2 Making your module threadsafe
X X
X X
X X X X X

Since 5.6.0, Perl has had support for a new type of threads called
interpreter threads (ithreads). These threads can be used explicitly
and implicitly.

Ithreads work by cloning the data tree so that no data is shared
between different threads. These threads can be used by using the C
module or by doing fork() on win32 (fake fork() support). When a
thread is cloned all Perl data is cloned, however non-Perl data cannot
be cloned automatically. Perl after 5.7.2 has support for the C
special subroutine. In C you can do whatever
you need to do,
like for example handle the cloning of non-Perl data, if necessary.
C will be called once as a class method for every package that has it
defined (or inherits it). It will be called in the context of the new thread,
so all modifications are made in the new area. Currently CLONE is called with
no parameters other than the invocant package name, but code should not assume
that this will remain unchanged, as it is likely that in future extra parameters
will be passed in to give more information about the state of cloning.

If you want to CLONE all objects you will need to keep track of them per
package. This is simply done using a hash and Scalar::Util::weaken().

Perl after 5.8.7 has support for the C special subroutine.
Like C, C is called once per package; however, it is
called just before cloning starts, and in the context of the parent
thread. If it returns a true value, then no objects of that class will
be cloned; or rather, they will be copied as unblessed, undef values.
For example: if in the parent there are two references to a single blessed
hash, then in the child there will be two references to a single undefined
scalar value instead.
This provides a simple mechanism for making a module threadsafe; just add
C_{at the top of the class, and C will
now only be called once per object. Of course, if the child thread needs
to make use of the objects, then a more sophisticated approach is
needed.

Like C, C is currently called with no parameters other
than the invocant package name, although that may change. Similarly, to
allow for future expansion, the return value should be a single C<0> or
C<1> value.

=head1 SEE ALSO

See L for general style issues related to building Perl
modules and classes, as well as descriptions of the standard library
and CPAN, L for how Perl's standard import/export mechanism
works, L and L for in-depth information on
creating classes, L for a hard-core reference document on
objects, L for an explanation of functions and scoping,
and L and L for more information on writing
extension modules.}}}