Free module definition software for linux

Objective Modula-2 programming language is a hybrid between Smalltalk and Modula-2 based on the object model and runtime of Objective-C.

The design is an example how native Cocoa/GNUstep support can be added to static imperative programming languages without implementing a bridge.

The projects scope encompasses the design of the Objective Modula-2 programming language and the implementation of a compiler to implement it. The initial compiler will generate Objective-C source code.

Module::Versions is a Perl module to handle versions of loaded modules with flexible result interface.

SYNOPSIS

use Module::Versions;

# Simple Interface
list Module::Versions; # prints formatted results to STDOUT
Module::Versions->list; # prints formatted results to STDOUT

# Shortcuts
$vers = get Module::Versions; # retrieves loaded modules

$vers = Module::Versions->get; # retrieves loaded modules

$array = Module::Versions->ARRAY; # returns array with version infos
$hash = Module::Versions->HASH; # returns hash with version infos

$list = Module::Versions->SCALAR; # returns text list with version infos
$csv = Module::Versions->CSV; # returns csv list with version infos
$xml = Module::Versions->XML; # returns xml struct with version infos
$xsd = Module::Versions->XSD; # returns xml schema of version infos
$dtd = Module::Versions->DTD; # returns DTD of version infos

# Individual Parameters
$vers = Module::Versions # retrieves mods and vars as defined
->new($mods,$vars)
->get($criteria);

$vers->list($fd,$mask); # prints formatted results to file
$vers->list($fd,$preform); # prints preformatted results to file
$vers->list($fd,&cb); # prints serialied results as handled
# in callback routine
$vers->data(&cb); # returns transformed results as
# defined in callback routine
# Individual formatted output
list Module::Versions(*LOG, %5d %1s %-20s %10s %-16s);
# prints individually formatted
# results to LOG
list Module::Versions(*DBIMPORT, %s|%s|%s);
# prints individually formatted
# results to Database Import file

list Module::Versions(*FD, SCALAR);# prints text list results to file
list Module::Versions(*FD, CSV); # prints csv list results to file
list Module::Versions(*FD, XML); # prints xml struct results to file
list Module::Versions(*FD, XSD); # prints xml schema to file
list Module::Versions(*FD, DTD); # prints DTD to file

list Module::Versions(*FD, ARRAY); # prints serialized results to file
list Module::Versions(*FD, HASH); # prints serialized results to file

Module::Versions->list(*LOG); # prints formatted results to LOG

# Pretty Compact
Module::Versions->list # prints formatted results on STDOUT
->list(*XML,XML); # prints xml struct results to XML file

Module::Versions->list # prints formatted results on STDOUT
->list(*XSD,XSD) # prints xml schema to XSD file
->list(*XML,XML); # prints xml struct results to XML file

Module::Versions->list # prints formatted results on STDOUT
->list(*DTD,DTD) # prints DTD to DTD file
->list(*XML,XML); # prints xml struct results to XML file

Module::Versions handles versions of loaded modules with a flexible result interface. The main goal is to get as much version informations as possible about a module or module list with a simple call interface and an absolutely flexible result interface. Module::Versions handles *loaded* and *loadable* modules.

The motivation for writing this module was the need for better support facilities to get informations about the used modules and versions in the productivity environment. Module::Versions allows shipping applications basically with something like a -version option (See Getopt::Long) but with expanded functions.

Module::Versions tries to read the loaded/loadable modules $VERSION. For extended purposes any private project version variables can be fetched ($_VERSION, $version, $REV, etc.).

Module::Versions has a flexible result interface to satisfy different needs: results can be lists and data structures with different formats - pre-formed ARRAY, HASH, SCALAR, CSV, XML/XSD/DTD and a full flexible user callback interface.
It is for example very simple to print a good formatted version list to the console and save a version.xml file (in conjunction with an xsd-schema) at the same time with an absolutely minimum of coding (SYNOPSIS, Pretty Compact) .
Module::Versions tries to load version.pm to support Perl 5.10.0s $VERSION formatting.

Sybase module for Python project provides a Python interface to the Sybase relational database system. The Sybase package supports all of the Python Database API, version 2.0 with extensions.
Enhancements:
- This release works with Python 2.5, Sybase 15, and 64-bit clients.
- It can also use native Python datetime types.
- The infamous bug "This routine cannot be called because another command structure has results pending."
- that appears in various cases has been corrected.
- Various bugs have been corrected.

SYNOPSIS

perl -MModule::AutoINC < script >

ABSTRACT

When Module::AutoINC is loaded, it will add itself to @INC and catch any requests for missing resources. If a Perl module is requested that has not been installed, then this will attempt to load it. Under Active State Perl (or any Perl where PPM is available), PPM will attempt to install it. Otherwise CPAN will be queried and, assuming that the module exists on CPAN, CPAN::Shell will be invoked to install it. Execution of the script continues after the requisite module has been installed.

Module::AutoINC is a slightly useful tool designed to streamline the process of installing the modules required by a script. By loading the Module::AutoINC module (usually via a "-MModule::AutoINC" command-line option), the user is registering a handler that will catch any attempt to use a module that does not exist on the local machine. In this case, the CPAN::Shell module will be invoked to search for the specified module and, if found, an attempt will be made to install the module. If successful, the module will be loaded and execution will continue as normal.

Imported Symbols

You can modify the behavior of the module slightly using several import symbols. All import symbols are case-insensitive.

If you import the special symbol force then the installation of the module(s) will be forced. The definition of a forced installation varies depending on whether you are installing using PPM or CPAN. See the relevant documentation for each system for more information.

You can override the installation method detection using the import symbols, cpan or ppm. cpan will cause CPAN to be used for module installation no matter whether PPM is available or not. ppm will attempt to install the module using PPM regardless of whether ppm is findable by Module::AutoINC. Of course, you should know what you are doing if you use these import symbols.

Examples

perl -MModule::AutoINC -MLingua::Num2Word=cardinal -le print cardinal("en", 42)

...will download and install Lingua::Num2Word and Lingua::EN::Num2Word.

perl -MModule::AutoINC=cpan -MLingua::Num2Word=cardinal -le print cardinal("de", 42)

...will then download and install (using CPAN, even under ActiveState Perl) Lingua::DE::Num2Word (German).

perl -MModule::AutoINC=force -MLingua::Num2Word=cardinal -le print cardinal("es", 42)

...will then download and install (forcefully) Lingua::ES::Numeros (Spanish).

Module::ThirdParty is a Perl module which can provide information for 3rd party modules (outside CPAN).
SYNOPSIS
use Module::ThirdParty;
if (is_3rd_party($module)) {
my $info = module_information($module);
print "$module is a known third-party Perl modulen",
" -> included in $info->{name} ($info->{url})n",
" -> made by $info->{author} ($info->{author_url})n"
} else {
print "$module is not a known third-party Perl modulen"
}
Perl modules can be roughly classified in three categories:
- core modules, included with the standard Perl distribution;
- CPAN modules, available from any CPAN mirror;
- third-party modules, including modules publicly available on the Internet (outside CPAN) and "closed" modules available only through commercial licenses.
The list of core modules is provided by Module::CoreList and the list of CPAN modules is in the file http://www.cpan.org/modules/02packages.details.txt.gz and provided by modules like CPANPLUS, but there was no module that listed third-party modules. This module tries to address this need by providing such a list.
Why bother in the first place? Because some CPAN modules specify such third-party software. Therefore installing them may not be as easy as other CPAN modules because one must first find and manually install the prerequisites. The aim of Module::ThirdParty is to provide basic information to installer shells like CPANPLUS and to give hints to the user.
Note that there is also another category of modules regarding dependencies problems: the ghost modules. Those are modules no longer present on the CPAN, but which still haunt it from old PREREQS. They can be found in the BackPAN graveyard, for which the only map is Parse::BACKPAN::Packages.

Jeta SSH Module provides a Horde SSH module.

Jeta is the Horde Application Frameworks wrapper module for the SSHTools Java SSH Applet.

Jeta is based on a java SSH client. It allows shell access to your web server, or to another machine if used with a port relay daemon (not provided).

Module::Reload::Selective can reload Perl modules during development.

SYNOPSIS

Instead of:

use Foobar::MyModule;

Do this:

use Module::Reload::Selective;
&Module::Reload::Selective->reload(qw(Foobar::MyModule));
Or, if you need the "import" semantics of "use", do this:

use Foobar::MyModule (@ImportArgs);

Do this:

use Module::Reload::Selective;
Module::Reload::Selective->reload(qw(Foobar::MyModule));

import Foobar::MyModule (@ImportArgs);

... then configure your server or other runtime environment settings to trigger Module::Reload::Selective to only kick in when you need.

For example: you could have it kick in only when the web server is running on a particular port number or particular (development) host.

Module::Build::Authoring are authoring Module::Build modules.

When creating a Build.PL script for a module, something like the following code will typically be used:

use Module::Build;
my $build = Module::Build->new
(
module_name => Foo::Bar,
license => perl,
requires => {
perl => 5.6.1,
Some::Module => 1.23,
Other::Module => >= 1.2, != 1.5, < 2.0,
},
);
$build->create_build_script;

A simple module could get away with something as short as this for its Build.PL script:

use Module::Build;
Module::Build->new(
module_name => Foo::Bar,
license => perl,
)->create_build_script;

The model used by Module::Build is a lot like the MakeMaker metaphor, with the following correspondences:

In Module::Build In ExtUtils::MakeMaker
--------------------------- ------------------------
Build.PL (initial script) Makefile.PL (initial script)
Build (a short perl script) Makefile (a long Makefile)
_build/ (saved state info) various config text in the Makefile

Any customization can be done simply by subclassing Module::Build and adding a method called (for example) ACTION_test, overriding the default test action. You could also add a method called ACTION_whatever, and then you could perform the action Build whatever.
For information on providing compatibility with ExtUtils::MakeMaker, see Module::Build::Compat and http://www.makemaker.org/wiki/index.cgi?ModuleBuildConversionGuide.