Free to call software for linux

Python Call Graph (pycallgraph) is a Python library that creates call graphs for Python programs

pycallgraph is quite new. It seems to work well and I will most likely improve it in the near future!

RPyC stands for Remote Python Call, a pun over remote procedure call. It is completely transparent and symmetrical. It is inspired by the work of eyal lotem (pybuild.sf.net) on pyinvoke, and was made for two purposes:
Learning the lowlevel of the python language attempting to improve pyinvoke by making the entire protocol symmetrical. This means the client can make requests to the server, and the server can reply with requests of its own (the client is also a server on its own). This typically means using callback functions.
The RPyC package comes with a full demo, showing (or showing-off) many of its features. As i said, its completely transparent and symmetrical, so you can write code just as you would write in the case of normal python programs.
demo 1 -- a simple client demo
# import the client
from Rpyc.Client import RpycSocketClient
# `hostname` is the name of the host running an Rpyc server
# the port parameter is optional
c = RpycSocketClient("hostname")
# now we are connected and can start messing around with stuff on the server
for filename in c.modules.os.listdir("/tmp"):
print "found file", filename
Enhancements:
- This release adds DeliveringNamespace, LoginError (instead of tlslites internal errors), __version__, deliver (the counterpart of obtain, which can now deliver and obtain functions as well), and isproxy (to test whether an object is a proxy).
- It improves memory consumption with __slots__ and the isinstance/issubclass mechanism.

Tk::callbacks allows specifying code for Tk to call.

SYNOPSIS

One can specify a callback in one of the following ways:

Without arguments:

... => ⊂name, ...
... => sub { ... }, ...
... => methodname, ...

or with arguments:

... => [ ⊂name ?, args ...? ], ...
... => [ sub { ... } ?, args...? ], ...
... => [ methodname ?, args...?], ...

Perl/Tk has a callback, where Tcl/Tk has a command string (i.e. a fragment of Tcl to be executed). A perl/Tk callback can take one of the following basic forms:

Reference to a subroutine ⊂name
Anonymous subroutine (closure) sub { ... }
A method name methodname

Any of these can be provided with arguments by enclosing them and the arguments in []. Here are some examples:

$mw->bind($class, " " => Delete);

This will call $widget->Delete, the $widget being provided (by bind) as the one where the Delete key was pressed.
While having bind provide a widget object for you is ideal in many cases it can be irritating in others. Using the list form this behaviour can be modified:

$a->bind(" ",[$b => Delete]);

because the first element $b is an object bind will call $b->Delete.

Note that method/object ordering only matters for bind callbacks, the auto-quoting in perl5.001 makes the first of these a little more readable:

$w->configure(-yscrollcommand => [ set => $ysb]);
$w->configure(-yscrollcommand => [ $ysb => set ]);

but both will call $ysb->set(args provided by Tk)
Another use of arguments allows you to write generalized methods which are easier to re-use:

$a->bind(" ",[Next,Page]);
$a->bind(" ",[Next,Line]);

This will call $a->Next(Page) or $a->Next(Line) respectively.

Note that the contents of the [] are evaluated by perl when the callback is created. It is often desirable for the arguments provided to the callback to depend on the details of the event which caused it to be executed. To allow for this callbacks can be nested using the Ev(...) "constructor". Ev(...) inserts callback objects into the argument list. When perl/Tk glue code is preparing the argument list for the callback it is about to call it spots these special objects and recursively applies the callback process to them.

EXAMPLES

$entry->bind( => [$w , validate, Ev([get])]);

$toplevel->bind(all, , [&unobscure, Ev(s)]);

$mw->bind($class, , [SetCursor, Ev(UpDownLine,1)]);

QWPython project is a Python-powered QuakeWorld server.

The core engine has been wrapped up as a Python module and altered to call back to Python to execute Quake game logic.

A QuakeC - Python translator is also included, along with pre-translated versions of Deathmatch and Capture-The-Flag.

Class::DispatchToAll Perl module can dispatch a method call to all inherited methods.

SYNOPSIS

package My::Class;
our @ISA=qw(SomeClass SomeOtherClass More::Classes);
use Class::DispatchToAll qw(dispatch_to_all);

my $self=bless {},My::Class # not a proper constructor, I know..

# this calls some_method in all Classes My::Class inherits from
# and all classes those classes inherit from, and all ... you get
# the point.
$self->dispatch_to_all(some_method);

# saves all return values from all calls in an array
my @returns=$self->dispatch_to_all(some_method);

See the Docs of Damian Conways Module Class::Delegation for a good introduction about Dispatching vs. Inheritance.

Class::DispatchToAll enables you to call all instantances of a method in your inheritance tree (or labyrinth..).

The standard Perl behaviour is to call only the lefternmost instance it can fing doing a depth first traversial.

Imagine the following class structure:
C
/
A B C::C
/ /
A::A D
/
My::Class

Perl will try to find a method in this mess in this order:

My::Class -> A::A -> A -> B -> D -> B -> C::C -> C
(Note that it will look twice in B because B is a parent of both A::A and D))

As soon as Perl finds the method somewhere, it will short-circuit out of its search and invoke the method.

And that is exactly the behaviour Class::DispatchToAll changes.

If you use dispatch_to_all (provided by Class::DispatchToAll) to call your method, Perl will look in all of the aforementioned packages and run all the methods it can find. It will even collect all the return values and return them to you as an array, if you want it too.

isdnMonitor saves call information (number, name, connection, and duration) in a MySQL database.

The project does inverse searches for German phone numbers, enables notifying clients via the Windows/SMB messaging service, and displays caller names on an LCD display via LCDproc.

Call Commander is a high-performance management system and call screening designed for use in professional talk-radio environments that integrates directly with a variety of popular broadcast telephone interfaces.
The system is designed to allow the easy acquisition, tracking, communication and archiving of caller information, along with tools to enable seamless communication between the various key talk show players (talent, producer, screener, etc).
Also provided is an automated Segment Clock to help keep things running on time.
Call Commander is highly configurable, with virtually every aspect of its on-screen appearance and functionality capable of being customized for the needs of a particular site. Visit our gallery of screen shots showing some of the possibilities available.
Call Commander runs on the popular GNU/Linux operating system, with clients also available for Microsoft Windows 98, 2000 and XP. It is freely available under the GNU General Public License.
Main features:
- Highly customizable and configurable.
- Comprehensive caller data acquisition, status tracking and archving.
- Point-to-point communication and alerting for Talk Show personnel.
- Synchronized, automatic segment clock.
- Works with a variety of broadcast telephone systems, including:
- Comrex/Gentner TS-612
- Telos 100 1A2 Interface
- Telos 100 Direct Interface
- Telos 2101
- Telos ONEx6
- Telos TWOx12
- Works with LAN, Internet and Dialup networking connections.
- Runs on the rock-solid GNU/Linux operating system.
- Totally free and open -- No dongles, unlock codes, software keys or other arbitrary limitations.