openKylin libimport-into-perl package

libimport-into-perl 1.002005-ok1 source package in openKylin

Changelog

libimport-into-perl (1.002005-ok1) yangtze; urgency=medium

  * Build for openKylin.

 -- openKylinBot <email address hidden>  Mon, 25 Apr 2022 22:03:04 +0800

Upload details

Uploaded by:
openKylinBot
Sponsored by:
luzp
Uploaded to:
Yangtze V1.0
Original maintainer:
Openkylin Developers
Architectures:
all
Section:
perl
Urgency:
Medium Urgency

Publishing See full publishing history

Series Pocket Published Component Section

Downloads

File Size SHA-256 Checksum
libimport-into-perl_1.002005.orig.tar.gz 7.6 KiB bd9e77a3fb662b40b43b18d3280cd352edf9fad8d94283e518181cc1ce9f0567
libimport-into-perl_1.002005-ok1.debian.tar.xz 1.9 KiB 0b32f3e0b67de976bd72ee4a5b90c10a362e44c87be92f07ad44a52846f0421b
libimport-into-perl_1.002005-ok1.dsc 1.9 KiB a916879bf4b184d610f44b33723be1e610caea647d5ee1e0cf0ce4700acc5860

View changes file

Binary packages built by this source

libimport-into-perl: module for importing packages into other packages

 Import::Into creates a global method import::into which you can call on
 any package to import it into another package. This is useful because
 there are many different ways to write exporters: some use Exporter, some
 use Sub::Exporter, some use Moose::Exporter, some use Exporter::Declare
 and some things are pragmas.
 .
 And if you want to re-export other things, you have to know which is which.
 Exporter subclasses provide export_to_level, but if they overrode their
 import method all bets are off. Sub::Exporter provides an into parameter
 but figuring out something used it isn't trivial. Pragmas need to have
 their import method called directly since they affect the current unit of
 compilation. Import::Into can be used to import packages into other packages
 without having to deal with the specific details of every exporting approach.