| Name : perl-Devel-Symdump
| |
| Version : 2.18
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : 1.59
| Date : 2024-08-05 17:26:28
|
| Group : Development/Libraries/Perl
| Source RPM : perl-Devel-Symdump-2.18-1.59.src.rpm
|
| Size : 0.03 MB
| |
| Packager : (none)
| |
| Summary : Dump symbol names or the symbol table
|
Description :
This little package serves to access the symbol table of perl.
* \'Devel::Symdump->rnew(AATTpackages)\'
returns a symbol table object for all subtrees below AATTpackages. Nested
Modules are analyzed recursively. If no package is given as argument, it
defaults to \'main\'. That means to get the whole symbol table, just do a
\'rnew\' without arguments.
The global variable $Devel::Symdump::MAX_RECURSION limits the recursion to
prevent contention. The default value is set to 97, just low enough to
survive the test suite without a warning about deep recursion.
* \'Devel::Symdump->new(AATTpackages)\'
does not go into recursion and only analyzes the packages that are given as
arguments.
* packages, scalars, arrays, hashes, functions, ios
The methods packages(), scalars(), arrays(), hashes(), functions(), ios(),
and (for older perls) unknowns() each return an array of fully qualified
symbols of the specified type in all packages that are held within a
Devel::Symdump object, but without the leading \'$\', \'AATT\' or \'%\'. In a scalar
context, they will return the number of such symbols. Unknown symbols are
usually either formats or variables that haven\'t yet got a defined value.
Note that scalar symbol table entries are a special case. If a symbol table
entry exists at all, presence of a scalar is currently unknowable, due to a
feature of Perl described in perlref/Making References point 7. For
example, this package will mark a scalar value \'$foo\' as present if any of
\'AATTfoo\', \'%foo\', \'&foo\' etc. have been declared or used.
* as_string
* as_HTML
As_string() and as_HTML() return a simple string/HTML representations of
the object.
* diff
Diff() prints the difference between two Devel::Symdump objects in human
readable form. The format is similar to the one used by the as_string
method.
* isa_tree
* inh_tree
Isa_tree() and inh_tree() both return a simple string representation of the
current inheritance tree. The difference between the two methods is the
direction from which the tree is viewed: top-down or bottom-up. As I\'m
sure, many users will have different expectation about what is top and what
is bottom, I\'ll provide an example what happens when the Socket module is
loaded:
* % print Devel::Symdump->inh_tree
AutoLoader
DynaLoader
Socket
DynaLoader
Socket
Exporter
Carp
Config
Socket
The inh_tree method shows on the left hand side a package name and indented
to the right the packages that use the former.
* % print Devel::Symdump->isa_tree
Carp
Exporter
Config
Exporter
DynaLoader
AutoLoader
Socket
Exporter
DynaLoader
AutoLoader
The isa_tree method displays from left to right ISA relationships, so
Socket IS A DynaLoader and DynaLoader IS A AutoLoader. (Actually, they were
at the time this manpage was written)
You may call both methods, isa_tree() and inh_tree(), with an object. If
you do that, the object will store the output and retrieve it when you call
the same method again later. The typical usage would be to use them as
class methods directly though.
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-D/openSUSE_Tumbleweed/noarch |
