Free perl interface livingston portmaster 2 software for linux

Imager::interface.pod decribes the C level virtual image interface.

The Imager virtual interface aims to allow image types to be created for special purposes, both to allow consistent access to images with different sample sizes, and organizations, but also to allow creation of synthesized or virtual images.
This is a C level interface rather than Perl.

GnuPG::Interface is a Perl interface to GnuPG.

SYNOPSIS

# A simple example
use IO::Handle;
use GnuPG::Interface;

# settting up the situation
my $gnupg = GnuPG::Interface->new();
$gnupg->options->hash_init( armor => 1,
homedir => /home/foobar );

# Note you can set the recipients even if you arent encrypting!
$gnupg->options->push_recipients( ftobin@cpan.org );
$gnupg->options->meta_interactive( 0 );

# how we create some handles to interact with GnuPG
my $input = IO::Handle->new();
my $output = IO::Handle->new();
my $handles = GnuPG::Handles->new( stdin => $input,
stdout => $output );

# Now well go about encrypting with the options already set
my @plaintext = ( foobar );
my $pid = $gnupg->encrypt( handles => $handles );

# Now we write to the input of GnuPG
print $input @plaintext;
close $input;

# now we read the output
my @ciphertext = ;
close $output;

waitpid $pid, 0;

GnuPG::Interface and its associated modules are designed to provide an object-oriented method for interacting with GnuPG, being able to perform functions such as but not limited to encrypting, signing, decryption, verification, and key-listing parsing.

How Data Member Accessor Methods are Created

Each module in the GnuPG::Interface bundle relies on Class::MethodMaker to generate the get/set methods used to set the objects data members. This is very important to realize. This means that any data member which is a list has special methods assigned to it for pushing, popping, and clearing the list.

Understanding Bidirectional Communication

It is also imperative to realize that this package uses interprocess communication methods similar to those used in IPC::Open3 and "Bidirectional Communication with Another Process" in perlipc, and that users of this package need to understand how to use this method because this package does not abstract these methods for the user greatly. This package is not designed to abstract this away entirely (partly for security purposes), but rather to simply help create proper, clean calls to GnuPG, and to implement key-listing parsing. Please see "Bidirectional Communication with Another Process" in perlipc to learn how to deal with these methods.

Using this package to do message processing generally invovlves creating a GnuPG::Interface object, creating a GnuPG::Handles object, setting some options in its options data member, and then calling a method which invokes GnuPG, such as clearsign. One then interacts with with the handles appropriately, as described in "Bidirectional Communication with Another Process" in perlipc.

perlrpcgen is a Perl module that can generate Perl interfaces from ONC RPC interface definitions.

SYNOPSIS

perlrpcgen [--makefile] [--all] [--client] [--server] [--data] [--constants] [--module module] [--typemap typemap] [--fork] [--perl perl] [--cc cc] [--rpclibs rpclibs] rpcfile.x

perlrpcgen builds a set of Perl extensions and a server shell from an ONC RPC interface definition. For an interface Foo, perlrpcgen creates modules Foo::Client, Foo::Data, and Foo::Constants. Foo::Client contains routines for creating a Foo client and making remote procedure calls via the client. Foo::Data contains routines for creating and manipulating the data structures defined in the Foo interface. Foo::Constants contains functions to retrieve the constants defined in the Foo interface.

OPTIONS

The option parsing uses Getopt::Long, so you can abbreviate option names.

--makefile

Generates a top-level Makefile which will build all the pieces. Include all the other options you want so theyll be propagated to the Makefile.

--all

Implies --client, --server, --data, and --constants. This is usually what you want.

--client

Generates Foo::Client module.

--server

Generates Foo/server/foo_svc.

--data

Generates Foo::Data module.

--constants

Generates Foo::Constants module.

--module module

Sets the basename of the modules. If not given, the name defaults to the basename of the interface file.

--typemap typemap

Uses the given typemap during stub generation. This option can be specified many times. perlrpcgen generates a typemap for the data structures in the interface, but you also need the main Perl typemap.

--fork

Munges the server shell code so that it forks for each request. You probably dont want to do this (its better to prefork several processes when you start the server and let them fight over accept() calls).

--perl perl

Sets the Perl binary against which extensions should be built. Defaults to the Perl you used to install perlrpcgen.

--cc cc

Sets the C compiler to use. Defaults to the compiler used when building Perl.

--rpclibs rpclibs

Sets the RPC libraries to link against. Defaults to -lnsl -lrpcsvc.

Audio::Mad::Stream is a Perl interface to mad_stream structure.

SYPNOSIS

my $stream = new Audio::Mad::Stream ($options);
$stream->buffer($scalar);

my $remain = substr($scalar, $stream->next_frame);
my $position = $stream->this_frame;

$stream->skip($position + 400);
$stream->sync();

$options = $stream->options();
$options |= MAD_OPTION_IGNORECRC;
$stream->options($options);

unless ($stream->err_ok()) {
print "error code was: " . $stream->error() . "n";
}

This package provides an interface to the underlying mad_stream structure used in the decoder library. Almost all of the methods from the library are implemented, and work on regualar perl data types.

DCE::Status is a Perl interface of DCE status codes.

SYNOPSIS

use DCE::Status;

$errstr = error_inq_text($status);

tie $status => DCE::Status;

When a $scalar is tied to the DCE::Status class, it has a different value depending on the context it is evaluated in, similar to the magic $! variable. When evaluated in a numeric context, the numeric value is returns, otherwise, the string value obtained from dce_error_inq_text is returned.

EXPORTS

error_inq_text

Equivalent to the dce_error_inq_text function.

$errstr = error_inq_text($status);

WebService::Upcoming is a Perl interface to the Upcoming API.

SYNOPSIS

use WebService::Upcoming;

my $upco = new WebService::Upcoming("*** UPCOMING API KEY HERE ***");
my $objc = $upco->call("event.search",
{
"search_text" => "music"
});
die("ERROR: ".$upco->err_text()."n") if (!defined($objc));
foreach (@{$objc})
{
print("EVENT: ".$_->name()." on ".$_->start_date()."n");
}

A simple interface for using the Upcoming API.
WebService::Upcoming is a subclass of LWP::UserAgent, so all of the various proxy, request limits, caching, and other features are available.

Teamspeak is a Perl interface to administrate Teamspeak-Server.

SYNOPSIS

use Teamspeak;
my $t = Teamspeak->new(
timeout => ,
port => ,
host =>
);

You can connect to a Teamspeak-Server in four different Connection-Types: 1. Telnet 2. MySQL or MySQL::Lite 3. Web-Frontend 4. Teamspeak-Client is using UDP

Every Connection-Type can only use a part of all available Methods.