libfuture-perl 0.21-1 source package in Ubuntu

Changelog

libfuture-perl (0.21-1) unstable; urgency=medium


  * New upstream release.
  * Update years of packaging copyright.

 -- gregor herrmann <email address hidden>  Wed, 01 Jan 2014 23:14:15 +0100

Upload details

Uploaded by:
Debian Perl Group
Uploaded to:
Sid
Original maintainer:
Debian Perl Group
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section

Builds

Trusty: [FULLYBUILT] i386

Downloads

File Size SHA-256 Checksum
libfuture-perl_0.21-1.dsc 2.1 KiB 1f58f331b73299e5cc181360537eb1ac7d792ed8be04730e6af26a66efcef5c0
libfuture-perl_0.21.orig.tar.gz 58.7 KiB e2bebd2e9ca78adcc9a505b68406ed13078531c029c9c5c4e3b86099ed9388d7
libfuture-perl_0.21-1.debian.tar.gz 2.1 KiB de31c22c091c149d4ad68a9ebbcd7c3de1e422b5bc5f1ffb7c4f7d1eb6b030d2

Available diffs

No changes file available.

Binary packages built by this source

libfuture-perl: module for operations awaiting completion

 A Future object represents an operation that is currently in progress, or
 has recently completed. It can be used in a variety of ways to manage the
 flow of control, and data, through an asynchronous program.
 .
 Some futures represent a single operation and are explicitly marked as ready
 by calling the done or fail methods. These are called "leaf" futures here,
 and are returned by the new constructor.
 .
 Other futures represent a collection sub-tasks, and are implicitly marked as
 ready depending on the readiness of their component futures as required.
 These are called "dependent" futures here, and are returned by the various
 wait_* and need_* constructors.
 .
 It is intended that library functions that perform asynchonous operations
 would use Future objects to represent outstanding operations, and allow their
 calling programs to control or wait for these operations to complete. The
 implementation and the user of such an interface would typically make use of
 different methods on the class. The methods below are documented in two
 sections; those of interest to each side of the interface.