Free function set software for linux

Getopt::Function is a Perl module to provide mixed options with help information.

SYNOPSIS

use Getopt::Function qw(maketrue makevalue);
$::opthandler = new Getopt::Function
[ ], { => [ , ,
] }
$result = GetOptions (...option-descriptions...);
$::opthandler->std_opts;
$::opthandler->check_opts;

The aim of this module is to make it easy to provide sophisticated and complex interfaces to commands in a simple to use and clear manner with proper help facilities.

It is designed to do this by making it possible to write the options, with documentation and subroutines to implement them, directly into a hash and then call the appropriate ones as options detected on the command line.

FuncPlotter is a combined Java application and applet for displaying two-dimensional plots of explicit functions in one variable (i.e., functions of the form y = f(x), where f(x) is an arbitrary function composed from a set of common mathematical operators).
Up to 20 functions can be plotted simultaneously, and sets of functions can be loaded and saved.
Enhancements:
Modifications:
- The function-list UI component has been modified so that the position of a function in the list can now be changed by dragging the function up or down the list with the left mouse button.
- Configuration parameters have been added to allow the FuncPlotter applet to display specified functions when it starts up.

CoreLinux++ Function Load Library (libclfll++) takes advantage of the abstract Library Load framework in the CoreLinux libclfw++ library by providing management of loading Linux shared libraries.
Application developers define function objects as wrappers and can then dynamically load the functions. It is very useful for implementing a framework for plug-ins.
Main features:
- Enlist members ( for requirements, analysis, design, and development )
- Formalize conventions for Object Oriented Analysis (OOA) and Design (OOD).
- Formalize standards and conventions for C++ code style.
- Gather requirements. Perform OOA and OOD using UML as the modeling language.
- Implement designs and example drivers.
- Develop utilities and applications for Linux that are CoreLinux++ certified
- Showcase CoreLinux++ certified applications by others

Timos rescue CD set provides an easy way to generate bootable CDROMs with a ready-to-use rescue system on them. The system is designed to be fully customizable and easy to build.
The rescue system includes reiserfs, parted, partimage, nmap, w3m, bash, sshd, telnetd, ftpd, and nfsd. It is based on Debians "Sarge" release. LILO, syslinux, isolinux, and GRUB are supported.
The project is evolving more and more into a "Debian on CD" project, which means that its use is not limited to a rescue CD; it is also possible to install a whole Debian system on CD.
Enhancements:
- the cdrecord script was buggy - fixed

B::Utils is a helper functions for op tree manipulation.

SYNOPSIS

use B::Utils;


These functions make it easier to manipulate the op tree.

FUNCTIONS

all_starts

all_roots

Returns a hash of all of the starting ops or root ops of optrees, keyed to subroutine name; the optree for main program is simply keyed to __MAIN__.

Note: Certain "dangerous" stashes are not scanned for subroutines: the list of such stashes can be found in @B::Utils::bad_stashes. Feel free to examine and/or modify this to suit your needs. The intention is that a simple program which uses no modules other than B and B::Utils would show no addition symbols.

This does not return the details of ops in anonymous subroutines compiled at compile time. For instance, given

$a = sub { ... };

the subroutine will not appear in the hash. This is just as well, since theyre anonymous... If you want to get at them, use...

anon_subs()

This returns an array of hash references. Each element has the keys "start" and "root". These are the starting and root ops of all of the anonymous subroutines in the program.

$op->oldname

Returns the name of the op, even if it is currently optimized to null. This helps you understand the stucture of the op tree.

$op->kids

Returns an array of all this ops non-null children, in order.

$op->first
$op->last
$op->other

Normally if you call first, last or other on anything which is not an UNOP, BINOP or LOGOP respectivly it will die. This leads to lots of code like:

$op->first if $op->can(first);

B::Utils provides every op with first, last and other methods which will simply return nothing if it isnt relevent.

$op->parent

Returns the parent node in the op tree, if possible. Currently "possible" means "if the tree has already been optimized"; that is, if were during a CHECK block. (and hence, if we have valid next pointers.)

In the future, it may be possible to search for the parent before we have the next pointers in place, but itll take me a while to figure out how to do that.

$op->previous

Like $op->next, but not quite.

walkoptree_simple($op, &callback, [$data])

The B module provides various functions to walk the op tree, but theyre all rather difficult to use, requiring you to inject methods into the B::OP class. This is a very simple op tree walker with more expected semantics.

The &callback is called at each op with the op itself passed in as the first argument and any additional $data as the second.

All the walk functions set $B::Utils::file and $B::Utils::line to the appropriate values of file and line number in the program being examined. Since only COPs contain this information it may be unavailable in the first few callback calls.

walkoptree_filtered($op, &filter, &callback, [$data])

This is much the same as walkoptree_simple, but will only call the callback if the filter returns true. The filter is passed the op in question as a parameter; the opgrep function is fantastic for building your own filters.

walkallops_simple(&callback, [$data])

This combines walkoptree_simple with all_roots and anon_subs to examine every op in the program. $B::Utils::sub is set to the subroutine name if youre in a subroutine, __MAIN__ if youre in the main program and __ANON__ if youre in an anonymous subroutine.

walkallops_filtered(&filter, &callback, [$data])

Same as above, but filtered.

Bio::NEXUS::WeightSet is a Perl module that represents column weights in alignment ( for each character).

SYNOPSIS

new Bio::NEXUS::WeightSet($name, @weights, $iswt);

A module representing column weights in alignment (for each character)

METHODS

new

Title : new
Usage : $node = new Bio::NEXUS::WeightSet($name, @weights);
Function: Creates a new Bio::NEXUS::WeightSet object
Returns : Bio::NEXUS::WeightSet object
Args : none

set_weights

Title : set_weights
Usage : $weight->set_weights(@weights);
Function: stores it in the list weights
Returns : none
Args : list of weights

get_weights

Title : get_weights
Usage : @wts=@{$weightset->get_weights()};
Function: Returns the weights array
Returns : reference to array containing weights
Args : none

select_weights

Title : select_weights
Usage : $set->select_weights($columns);
Function: select a subset of characters
Returns : new self with subset of weights
Args : column numbers

is_wt

Title : is_wt
Usage : croak unless $weight->is_wt();
Function: Returns if object has weights (1 yes, 0 no)
Returns : weight existence (integer)
Args : none

set_name

Title : set_name
Usage : $weight->set_name($name);
Function: Sets the name of the weightset
Returns : none
Args : name (string)

get_name

Title : get_name
Usage : $name=$weight->get_name();
Function: Returns the name of the weightset
Returns : name (string)
Args : none

equals

Name : equals
Usage : $set->equals($another);
Function: compare if two WeightSet objects are equal
Returns : boolean
Args : an WeightSet object

DBIx::Recordset is a Perl extension for DBI recordsets.

SYNOPSIS

use DBIx::Recordset;

# Setup a new object and select some recods...
*set = DBIx::Recordset -> Search ({!DataSource => dbi:Oracle:....,
!Table => users,
$where => name = ? and age > ?,
$values => [richter, 25] }) ;

# Get the values of field foo ...
print "First Records value of foo is $set[0]{foo}n" ;
print "Second Records value of foo is $set[1]{foo}n" ;
# Get the value of the field age of the current record ...
print "Age is $set{age}n" ;

# Do another select with the already created object...
$set -> Search ({name => bar}) ;

# Show the result...
print "All users with name bar:n" ;
while ($rec = $set -> Next)
{
print $rec -> {age} ;
}

# Setup another object and insert a new record
*set2 = DBIx::Recordset -> Insert ({!DataSource => dbi:Oracle:....,
!Table => users,
name => foo,
age => 25 }) ;


# Update this record (change age from 25 to 99)...
$set -> Update ({age => 99}, {name => foo}) ;

DBIx::Recordset is a perl module for abstraction and simplification of database access.

The goal is to make standard database access (select/insert/update/delete) easier to handle and independend of the underlying DBMS. Special attention is made on web applications to make it possible to handle the state-less access and to process the posted data of formfields, but DBIx::Recordset is not limited to web applications.

DBIx::Recordset uses the DBI API to access the database, so it should work with every database for which a DBD driver is available (see also DBIx::Compat).
Most public functions take a hash reference as parameter, which makes it simple to supply various different arguments to the same function. The parameter hash can also be taken from a hash containing posted formfields like those available with CGI.pm, mod_perl, HTML::Embperl and others.
Before using a recordset it is necessary to setup an object. Of course the setup step can be made with the same function call as the first database access, but it can also be handled separately.

Most functions which set up an object return a typglob. A typglob in Perl is an object which holds pointers to all datatypes with the same name. Therefore a typglob must always have a name and cant be declared with my. You can only use it as global variable or declare it with local. The trick for using a typglob is that setup functions can return a reference to an object, an array and a hash at the same time.

The object is used to access the objects methods, the array is used to access the records currently selected in the recordset and the hash is used to access the current record.

If you dont like the idea of using typglobs you can also set up the object, array and hash separately, or just set the ones you need.

Devel::TraceFuncs is a Perl module with trace function calls as they happen.

SYNOPSIS

Usage:

require Devel::TraceFuncs;

max_trace_depth 5;
trace_file "foo.out";
trace_file $file_handle;

sub foo {
IN(my $f, "a message");

DEBUG "hellooo!";
}

Devel::TraceFuncs provides utilities to trace the execution of a program. It can print traces that look something like:

+-> global: 0
| +-> main::fo(4, 5) (in ./t.pm:32): now then
| | +-> main::fp(4, 5) (in ./t.pm:19)
| | | +-> main::fq() (in ./t.pm:13)
| | | | que pee doll (in ./t.pm:8)
| | | +-< main::fq() (in ./t.pm:13)
| | | cee dee (in ./t.pm:14)
| | +-< main::fp(4, 5) (in ./t.pm:19)
| | ha
| | hs (in ./t.pm:20)
| +-< main::fo(4, 5) (in ./t.pm:32): now then
| done (in ./t.pm:34)
+-< global: 0

IN

A trace begins when a function calls IN. A myd variable is passed in, such that when that function exits, the destructor for the variable is called. If this trace is to be printed, the opening line of the trace in printed at this time. Any other parameters are concatenated together, and printed on both the opening and closing lines of the trace.

I wish the syntax could be a little nicer here, but I couldnt find anything in perl that resembles Tcls uplevel or upvar commands. If I was one of the perl gods, I could have figured out a way to do something like perl5db.pl:

sub sub {
# create a new subroutine, with a myd TraceFunc object
}

DEBUG

Print some text to the trace file, at the correct depth in the trace. If the last parameter ends in "!", the arguments are printed, regardless of current depth.

trace_file

trace_file takes one argument, which is either a file name or an open file handle. All trace output will go to this file.

max_trace_depth

To avoid lots of nesting, particularly from recursive function calls, you can set the maximum depth to be traced. If this is -1 (the default), all levels of functions are traced. If it is 0, no trace output occurs, except for DEBUG statements that end in "!".