Free cds global software for linux

vars::global is a Perl module that tries to make global variables a little safer.

SYNOPSIS

# In the place/package where we want to create globals
use vars::global create => qw( $foo @bar %baz );

# Add some more global symbols
vars::global->create(qw( $hello @world %now ));

# Somewhere else, where we need to access those globals
use vars::global qw( $foo @bar %baz );

# Dont try to use globals that do not exist
use vars::global qw( $Foo ); # typo, croaks
use vars::global qw( @inexistent ); # we dont create by default
# use create as above

# You can also import and create new globals
use vars::global qw( $foo %baz ), create => qw( $hey @joe );

# If youre lazy, you can import all the globals defined so far
use vars::global :all;

This module lets you define global variables and gain a slight advantage over blind use of package variables.

The global variables live inside the vars::global package, with the names given by the user. Where the advantage? Its two-fold:

there is an import mechanism that lets you access the global variable without the need to fully qualify its name (i.e. using $foo instead of $vars::global::foo);
the import mechanism ensures that you can import only the global variables that have been explicitly declared so far, which reduces the possibility of a typo.
If you have already "created" the global variable $foo, the import operation is equivalent to do:
*{__PACKAGE__ . ::foo} = $vars::global::foo;
that is, the package variable in the current package is made an alias for the global variable.

The anti-typo check is simply obtained by doing a check before the above import.
Typical usage is as follows:

creation

Early in the module or in the program you create variables prepending the create word, as follows:

use vars::global create => qw( $foo @bar %baz );

access

In the modules where you need to access a given global variable, you can import them very simply:

use vars::global qw( $foo %baz ); # I dont need @bar here ;)

The creation step above automatically imports all the new globals into the current package.

Global Assassin is a text-based action game.

The Global Assassin game is a multiplayer, shoot-em-up game set in the first person, and yet its text-based.

The year is 2035, and robots have taken over the Earth. Most humans died during the invasion or were forced to flee the planet. You are part of a small resistance that has managed to survive underground and is now prepared to strike back.

As a trained assassin, your objective is to return to the Earths surface, stealthily move through the worlds major cities, and systematically rid the planet of its invaders.

The details of the game are as follows.

The battlefield consists of 20 cities around the globe.

These cities have been connected for your mission by an ellaborate portal system.

Use the portals to move between cities as you search for and destroy the robots.

You are armed with a gun, bullets, and grenades.

To successfully strike an invader, you and your target must occupy the same city at the precise moment you attack.

You can lay a mine in a given city, and the very next player to enter that city trips the mine.

You remain alive as long as you have health points.

Over time, you automatically earn back health points, bullets, and grenades.

This is a multiplayer game. You may or may not be the only assassin on the planet!

JSignal is a loose port of the signal system implemented by GTKs GLib. JSignal project uses signals and handlers to allow for the registration of callback functions to events.
To use JSignal those classes which will emit signals (cause events) must register the signals that each class will emit. Note that if a class extends another class (has a superclass) it will inherit any signals registered by the parent class and can emit those signals as well. In addition a new global-type of signal can be registered which is class non-specific. Any class can emit a global signal.
After you have a class with registered signals you can begin connecting callback functions to those signals. Callback functions are connected (registered to listen for) to signals by specifying the signal and the object instance that will emit that signal; this registration results in the creation of a handler.
Multiple handlers can be configured for the same signal on the same object instance. In addition to instance-specific signal handlers a handler can also be registered to execute when a global signal (created using j_signal_new_global) is emitted; again, regardless of emitting instance. Note that when a global signal is emitted by an instance those handlers that are registered globally (using j_signal_handler_connect_global) will be executed BEFORE any instance-specific handlers.
To emit a signal - thus causing an event - the class which registered the signal should use the j_signal_emit function and pass any additional information to the callback function via the event detail argument. This detail object should be an array of name => value pairs.
Illustrative examples are provided below.
Note: In order for signal inheritance to work properly it is recommended that a classs prototype be given a parent member which points to the constructor of the classs superclass.
Main features:
- Multiple Handlers per Event
Multiple callback functions can be registered per signal per object instance.
- Signal Inheritance
The signals registered by an objects superclass are inherited by any extending child classes.
- Ordered Handler Execution
Like the DOM event handling system all handlers set to fire in response to a particular event fire in the order they were registered.
- Chained Handler Execution
Also like the DOM event handling model, when a handler returns a value of false any subsequent handlers will NOT be executed.
- Temporary Handler Blocking
Handlers can have blocks placed against them cumulatively; allowing for the selectively temporary disabling of handlers.
- Global Signals
Signals (as used in GLib) are class-specific. A signal registered under the class type of Integer can only be emitted by Integer instances. A global signal (registered using j_signal_new_global) can be emitted by any and all instances regardless of their class. This is essentially equivelant to registering a signal using the Javascript Object class type.
- Global Handlers
As signals are traditionally class specific it follows that handlers are instance specific. However global signals can be handled by both instance-specific handlers AND global handlers. A global handler is executed whenever a global signal is emitted, regardless of the emitting instance and its class type. Note that global handlers are executed BEFORE instance-specific handlers.

MySQL Global User Variables UDF is a MySQL extension to store persistent variables.

This shared library adds simple user functions to MySQL in order to keep persistent shared variables in memory. These variables and their values are available to all clients. Any data can be stored into these persistent variables, including BLOBs. Since updates are atomic and way faster than MEMORY tables, this is an easy and efficient way to handle counters and sequences.

Usage:

Storing a value

An unlimited number of user variables can be created, as long as memory is available.
The GLOBAL_STORE(, ) stores a new shared global variable.

Examples:

mysql> DO GLOBAL_STORE("online_users", 42);
mysql> DO GLOBAL_STORE("secret_key", "pajfUyfnd");

The GLOBAL_STORE() function always returns 1 unless an error occurred.

Fetching a value

Reading the value of a variable is the job of the GLOBAL_GET() function.
The value is returned, or NULL is the variable is undefined.

Example:

mysql> SELECT GLOBAL_GET("online_users;);
42

mysql> SELECT id FROM pxs WHERE secret_key = GLOBAL_GET("secret_key");
1

Atomic increments

A single function call can read the previous value, add an integer (that can be negative), and store the new value into the variable.

The function is GLOBAL_ADD(, ) and the return value is the new value of the variable.
Updates are always atomic, if the old value is 18 and you add 1, you will always get back 19.

Example:

mysql> DO GLOBAL_ADD("online_users", 1);
mysql> SELECT GLOBAL_ADD("online_users", -4);
39

If the value of a variable was a string, the new value is the increment:

mysql> SELECT GLOBAL_ADD("secret_key", 12);
12

Adding a value to an undefined variable returns NULL.
A handy variant is GLOBAL_ADDP(, ). GLOBAL_ADDP() is similar to GLOBAL_ADD() but returns the PREVIOUS value of the variable instead of the new one.

Example:

mysql> DO GLOBAL_SET("xxx", 10);
mysql> SELECT GLOBAL_ADDP("xxx", 1);
10
mysql> SELECT GLOBAL_ADDP("xxx", 1);
11

Installation:

On most systems, compiling and installing the library should be as simple as typing (as root):

make install

The shared library is installed as /usr/local/lib/udf_global_user_variables.so

If the base directory of your MySQL installation is not in /usr/local, just type:

make

and then copy udf_global_user_variables.so to the right location for UDFs on your system (maybe /usr/lib/).

The name of a variable is limited to 256 bytes. If that limit is too low for your specific application, just edit the MAX_NAME_LENGTH variable on top of the .c file and reinstall. Variable names can contain binary characters.

Values are limited to 65536 bytes. If that limit is too low for you, edit the MAX_VALUE_LENGTH variable and reinstall.

cdrtools (formerly cdrecord) creates home-burned CDs with a CDR/CDRW recorder. It works as a burn engine for several applications.
cdrtools supports CD recorders from many different vendors; all SCSI-3/mmc- and ATAPI/mmc-compliant drives should also work.
Supported features include IDE/ATAPI, parallel port, and SCSI drives, audio CDs, data CDs, and mixed CDs, full multi-session support, CDRWs (rewritable), TAO, DAO, RAW, and human-readable error messages.
cdrtools includes remote SCSI support and can access local or remote CD writers.
Enhancements:
- A +-1 size realloc() problem was fixed in TOC handling for cdda2wav.
- A workaround was added for a double free problem in mkisofs, introduced with multi-extent file support, that caused it to dump core on Cygwin.

Global Javadoc Viewer is a tiny application that allows you to conveniently browse multiple Javadoc sets simultaneously, using a single packages/classes hierarchy tree.

Global Javadoc Viewer pre-alfa version is not configurable, but useful, it allows to browse the next javadoc API sets:

- From the Internet: j2se 1.5, j2ee 1.4, hibernate and some others.
- From the local filesystem, in a UN*X box: all javadoc sets installed to the /usr/share/javadoc/ directory

SILC Map is an utility which can be used to visualize the topology of a SILC network. This project can create maps which indicate the exact global position of the servers and it can create HTML pages out of the information it gathers from the servers.

It is also possible to create a HTML map page which allows the user to click the servers on the map image to get more detailed information of the server. The links between the routers and servers can also be drawn on the map image.