Free base software for linux

C++ base is a base class suite contains several powerful c++ base classes for basic encapsulation of low level operating system calls and basic library functions.

Further packages you may access from this page require the installation of this base package

XML::SAX::Base is a base Perl class with SAX Drivers and Filters.

SYNOPSIS

package MyFilter;
use XML::SAX::Base;
@ISA = (XML::SAX::Base);

This module has a very simple task - to be a base class for PerlSAX drivers and filters. Its default behaviour is to pass the input directly to the output unchanged. It can be useful to use this module as a base class so you dont have to, for example, implement the characters() callback.

The main advantages that it provides are easy dispatching of events the right way (ie it takes care for you of checking that the handler has implemented that method, or has defined an AUTOLOAD), and the guarantee that filters will pass along events that they arent implementing to handlers downstream that might nevertheless be interested in them.

WRITING SAX DRIVERS AND FILTERS

Writing SAX Filters is tremendously easy: all you need to do is inherit from this module, and define the events you want to handle. A more detailed explanation can be found at http://www.xml.com/pub/a/2001/10/10/sax-filters.html.
Writing Drivers is equally simple. The one thing you need to pay attention to is NOT to call events yourself (this applies to Filters as well). For instance:
package MyFilter;
use base qw(XML::SAX::Base);

sub start_element {
my $self = shift;
my $data = shift;
# do something
$self->{Handler}->start_element($data); # BAD
}

The above example works well as precisely that: an example. But it has several faults: 1) it doesnt test to see whether the handler defines start_element. Perhaps it doesnt want to see that event, in which case you shouldnt throw it (otherwise itll die). 2) it doesnt check ContentHandler and then Handler (ie it doesnt look to see that the user hasnt requested events on a specific handler, and if not on the default one), 3) if it did check all that, not only would the code be cumbersome (see this modules source to get an idea) but it would also probably have to check for a DocumentHandler (in case this were SAX1) and for AUTOLOADs potentially defined in all these packages. As you can tell, that would be fairly painful. Instead of going through that, simply remember to use code similar to the following instead:

package MyFilter;
use base qw(XML::SAX::Base);

sub start_element {
my $self = shift;
my $data = shift;
# do something to filter
$self->SUPER::start_element($data); # GOOD (and easy) !
}

This way, once youve done your job you hand the ball back to XML::SAX::Base and it takes care of all those problems for you!

Note that the above example doesnt apply to filters only, drivers will benefit from the exact same feature.

Exception::Base is a Perl module with lightweight exceptions.
SYNOPSIS
# Use module and create needed exceptions
use Exception::Base (
Exception::IO,
Exception::FileNotFound => { message => File not found,
isa => Exception::IO },
);
# try / catch
try Exception eval {
do_something() or throw Exception::FileNotFound
message=>Something wrong,
tag=>something;
};
# Catch the Exception::Base, other exceptions throw immediately
if (catch Exception::Base my $e) {
# $e is an exception object for sure, no need to check if is blessed
if ($e->isa(Exception::IO)) { warn "IO problem"; }
elsif ($e->isa(Exception::Die)) { warn "eval died"; }
elsif ($e->isa(Exception::Warn)) { warn "some warn was caught"; }
elsif ($e->with(tag=>something)) { warn "something happened"; }
elsif ($e->with(qr/^Error/)) { warn "some error based on regex"; }
else { $e->throw; } # rethrow the exception
}
# the exception can be thrown later
$e = new Exception::Base;
$e->throw;
# try with array context
@v = try Exception::Base [eval { do_something_returning_array(); }];
# use syntactic sugar
use Exception::Base qw , Exception::IO;
try eval {
throw Exception::IO;
}; # dont forget about semicolon
catch my $e, [Exception::IO]; # Exception::Base is by default
This class implements a fully OO exception mechanism similar to Exception::Class or Class::Throwable. It does not depend on other modules like Exception::Class and it is more powerful than Class::Throwable. Also it does not use closures as Error and does not polute namespace as Exception::Class::TryCatch. It is also much faster than Exception::Class.
Main features:
- fast implementation of an exception object
- fully OO without closures and source code filtering
- does not mess with $SIG{__DIE__} and $SIG{__WARN__}
- no external modules dependencies, requires core Perl modules only
- implements error stack, the try/catch blocks can be nested
- shows full backtrace stack on die by default
- the default behaviour of exception class can be changed globally or just for the thrown exception
- the exception can be created with defined custom properties
- matching the exception by class, message or custom properties
- matching with string, regex or closure function
- creating automatically the derived exception classes ("use" interface)
- easly expendable, see Exception::System class for example

EB::Shell::Base is a generic class to build line-oriented command interpreters.

SYNOPSIS

package My::Shell;

use base qw(EB::Shell::Base);

sub do_greeting {
return "Hello!"
}

EB::Shell::Base is a slightly modified version of Shell::Base. It is modifed for the EekBoek program http://www.squirrel.nl/eekboek and NOT intended for general use. Please use Shell::Base instead.

Shell::Base is a base class designed for building command line programs. It defines a number of useful defaults, simplifies adding commands and help, and integrates well with Term::ReadLine.

After writing several REP (Read-Eval-Print) loops in Perl, I found myself wishing for something a little more convenient than starting with:

while(1) {
my $line = ;
last unless defined $line;

chomp $line;
if ($line =~ /^...

Features

Shell::Base provides simple access to many of the things I always write into my REPs, as well as support for many thing that I always intend to, but never find time for:
readline support

Shell::Base provides simple access to the readline library via Term::ReadLine, including built-in tab-completion and easy integration with the history file features.

If a subclass does want or need Term::ReadLine support, then it can be replaced in subclasses by overriding a few methods. See "Using Shell::Base Without readline", below.

Trivial to add commands

Adding commands to your shell is as simple as creating methods: the command foo is dispatched to do_foo. In addition, there are hooks for unknown commands and for when the user just hits , both of which a subclass can override.

Integrated help system

Shell::Base makes it simple to integrate online help within alongside your command methods. Help for a command foo can be retrieved with help foo, with the addition of one method. In addition, a general help command lists all possible help commands; this list is generated at run time, so theres no possibility of forgetting to add help methods to the list of available topics.

Pager integration

Output can be sent through the users default pager (as defined by $ENV{PAGER}, with a reasonable default) or dumped directly to STDOUT.

Customizable output stream(s)

Printing is handled through a print() method, which can be overridden in a subclass to send output anywhere.

Pre- and post-processing methods

Input received from readline() can be processed before it is parsed, and output from command methods can be post-processed before it is sent to print().

Automatic support for RC files

A simple RC-file parser is built in, which handles name = value type configuration files. This parser handles comments, whitespace, multiline definitions, boolean and (name, value) option types, and multiple files (e.g., /etc/foorc, $HOME/.foorc).

Shell::Base was originally based, conceptually, on Pythons cmd.Cmd class, though it has expanded far beyond what Cmd offers.

Games::LMSolve::Base is a base class for puzzle solvers.

SYNOPSIS

package MyPuzzle::Solver;

use Games::LMSolve::Base;

@ISA = qw(Games::LMSolve::Base);

# Override these methods:

sub input_board { ... }
sub pack_state { ... }
sub unpack_state { ... }
sub display_state { ... }
sub check_if_final_state { ... }
sub enumerate_moves { ... }
sub perform_move { ... }

# Optionally:
sub render_move { ... }
sub check_if_unsolvable { ... }

package main;

my $self = MyPuzzle::Solver->new();

$self->solve_board($filename);

This class implements a generic solver for single player games. In order to use it, one must inherit from it and implement some abstract methods. Afterwards, its interface functions can be invoked to actually solve the game.

Math::Symbolic::Base is a case class for symbols in symbolic calculations.

SYNOPSIS

use Math::Symbolic::Base;

This is a base class for all Math::Symbolic::* terms such as Math::Symbolic::Operator, Math::Symbolic::Variable and Math::Symbolic::Constant objects.

METHODS

Method to_string

Default method for stringification just returns the objects value.

Method value

value() evaluates the Math::Symbolic tree to its numeric representation.

value() without arguments requires that every variable in the tree contains a defined value attribute. Please note that this refers to every variable object, not just every named variable.

value() with one argument sets the objects value (in case of a variable or constant).

value() with named arguments (key/value pairs) associates variables in the tree with the value-arguments if the corresponging key matches the variable name. (Can one say this any more complicated?) Since version 0.132, an alternative syntax is to pass a single hash reference.

Example: $tree->value(x => 1, y => 2, z => 3, t => 0) assigns the value 1 to any occurrances of variables of the name "x", aso.

If a variable in the tree has no value set (and no argument of value sets it temporarily), the call to value() returns undef.

Method signature

signature() returns a trees signature.

In the context of Math::Symbolic, signatures are the list of variables any given tree depends on. That means the tree "v*t+x" depends on the variables v, t, and x. Thus, applying signature() on the tree that would be parsed from above example yields the sorted list (t, v, x).

Constants do not depend on any variables and therefore return the empty list. Obviously, operators dependencies vary.

Math::Symbolic::Variable objects, however, may have a slightly more involved signature. By convention, Math::Symbolic variables depend on themselves. That means their signature contains their own name. But they can also depend on various other variables because variables themselves can be viewed as placeholders for more compicated terms. For example in mechanics, the acceleration of a particle depends on its mass and the sum of all forces acting on it. So the variable acceleration would have the signature (acceleration, force1, force2,..., mass, time).

If youre just looking for a list of the names of all variables in the tree, you should use the explicit_signature() method instead.

Method explicit_signature

explicit_signature() returns a lexicographically sorted list of variable names in the tree.

See also: signature().

Method set_signature

set_signature expects any number of variable identifiers as arguments. It sets a variables signature to this list of identifiers.

Method implement

implement() works in-place!

Takes key/value pairs as arguments. The keys are to be variable names and the values must be valid Math::Symbolic trees. All occurrances of the variables will be replaced with their implementation.

Method replace

First argument must be a valid Math::Symbolic tree.

replace() modifies the object it is called on in-place in that it replaces it with its first argument. Doing that, it retains the original object reference. This destroys the object it is called on.

However, this also means that you can create recursive trees of objects if the new tree is to contain the old tree. So make sure you clone the old tree using the new() method before using it in the replacement tree or you will end up with a program that eats your memory fast.

fill_in_vars

This method returns a modified copy of the tree it was called on.

It walks the tree and replaces all variables whose value attribute is defined (either done at the time of object creation or using set_value()) with the corresponding constant objects. Variables whose value is not defined are unaffected. Take, for example, the following code:

$tree = parse_from_string(a*b+a*c);
$tree->set_value(a => 4, c => 10); # value of b still not defined.
print $tree->fill_in_vars();
# prints "(4 * b) + (4 * 10)"

Method simplify

Minimum method for term simpilification just clones.

Method descending_operands

When called on an operator, descending_operands tries hard to determine which operands to descend into. (Which usually means all operands.) A list of these is returned.

When called on a constant or a variable, it returns the empty list.

Of course, some routines may have to descend into different branches of the Math::Symbolic tree, but this routine returns the default operands.

The first argument to this method may control its behaviour. If it is any of the following key-words, behaviour is modified accordingly:

default -- obvious. Use default heuristics.

These are all supersets of default:
all -- returns ALL operands. Use with caution.
all_vars -- returns all operands that may contain vars.

Acme::MorningMusume::Base is a baseclass of the class represents each member of Morning Musume.

SYNOPSIS

use Acme::MorningMusume;

my $musume = Acme::MorningMusume->new;

# retrieve the members as a list of
# Acme::MorningMusume::Base based objects
my @members = $musume->members;

for my $member (@members) {
my $name_ja = $member->name_ja;
my $first_name_ja = $member->first_name_ja;
my $family_name_ja = $member->family_name_ja;
my $name_en = $member->name_en;
my $first_name_en = $member->first_name_en;
my $family_name_en = $member->family_name_en;
my $nick = $member->nick; # arrayref
my $birthday = $member->birthday; # Date::Simple object
my $age = $member->age;
my $blood_type = $member->blood_type;
my $hometown = $member->hometown;
my $emoticon = $member->emoticon; # arrayref
my $class = $member->class;
my $graduate_date = $member->graduate_date; # Date::Simple object

my $count;
my $images = $member->images(limit => 5);
while (my $image = $images->next) {
$count++;
my $content_url = $image->content_url;
my $context_url = $image->context_url;
$image->save_content(base => image . $count);
$image->save_context(base => page . $count);
}
}

Acme::MorningMusume::Base is a baseclass of the class represents each member of Morning Musume.