libfuture-perl 0.39-1 source package in Ubuntu


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

  [ Salvatore Bonaccorso ]
  * Update Vcs-* headers for switch to

  [ gregor herrmann ]
  * New upstream release.
  * Update years of upstream and packaging copyright.
  * Declare compliance with Debian Policy 4.2.1.

 -- gregor herrmann <email address hidden>  Mon, 24 Sep 2018 17:23:45 +0200

Upload details

Uploaded by:
Debian Perl Group on 2018-09-24
Uploaded to:
Original maintainer:
Debian Perl Group
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Disco release on 2019-01-22 main misc


Disco: [FULLYBUILT] amd64


File Size SHA-256 Checksum
libfuture-perl_0.39-1.dsc 2.2 KiB dd52ffe565ae10425fc603d87ce58cf2ec07bf4cd24c0d8a9d034515c5e28294
libfuture-perl_0.39.orig.tar.gz 86.8 KiB 1fdd988fabf477ad57156c8f9c1948c8037d7851830e8f37ae74e5a0ee4b6b45
libfuture-perl_0.39-1.debian.tar.xz 3.3 KiB 9a47967c5216fd9f891387dbf5e88a03a12fde4f7e960e37acf98ed25e795369

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 asynchronous 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.