(GPL-1.0-or-later or Artistic-1.0-perl) and (GPL-2.0-or-later or Artistic-1.0-perl) and MIT and UCD and Public Domain and BSD
((Artistic-1.0-Perl OR GPL-1.0-or-later) AND Artistic-2.0)
(GPL-1.0-or-later or Artistic-1.0-perl) and MIT and UCD
Simple platform independent e-mail from your perl script. Only requires Perl 5 and a network connection.
acquired package info from repodata DB: repodata/69e709f4d2852d98f12867a74015d19384fe2727ff670fd70178cdde80b1e77e-primary.sqlite.bz2
The Encode module provides the interface between Perl strings and the rest of the system. Perl strings are sequences of characters.
MIME::Lite is a simple, standalone module which can generate (not parse) MIME messages. Specifically, you can use it to output a simple, decent single- or multi-part message which may have text or binary attachments. And you do not have to install Mail:: or MIME:: modules.
Build an optimized subroutine parameter validator once, use it forever
Create a customized, optimized, non-lobotomized, uncompromised, and thoroughly specialized parameter checking subroutine.
One shortcoming of the CPAN clients that currently exist is that they have no way of specifying conflicting downstream dependencies of modules. This module attempts to work around this issue by allowing you to specify conflicting versions of modules separately, and deal with them after the module is done installing. For instance, say you have a module Foo, and some other module Bar uses Foo. If Foo were to change its API in a non-backwards-compatible way, this would cause Bar to break until it is updated to use the new API. Foo can't just depend on the fixed version of Bar, because this will cause a circular dependency (because Bar is already depending on Foo), and this doesn't express intent properly anyway - Foo doesn't use Bar at all. The ideal solution would be for there to be a way to specify conflicting versions of modules in a way that would let CPAN clients update conflicting modules automatically after an existing module is upgraded, but until that happens, this module will allow users to do this manually.
Expose PL_dirty, the flag that marks global destruction
Perl's global destruction is a little tricky to deal with with respect to finalizers because it's not ordered and objects can sometimes disappear.
The Carp routines are useful in your own modules because they act like die() or warn(), but with a message which is more likely to be useful to a user of your module. In the case of cluck, confess, and longmess that context is a summary of every call in the call-stack. For a shorter message you can use carp or croak which report the error as being from where your module was called. There is no guarantee that that is where the error was, but it is a good educated guess.
Minimal try/catch with proper preservation of $@
This module provides bare bones try/catch statements that are designed to minimize common mistakes with eval blocks, and NOTHING else.
A highly capable, feature-rich programming language
Perl 5 is a highly capable, feature-rich programming language with over 30 years of development. Perl 5 runs on over 100 platforms from portables to mainframes and is suitable for both rapid prototyping and large scale development projects.
An interface to the UNIX syslog(3) program
Sys-Syslog is an interface to the UNIX syslog(3) program. Call syslog() with a string priority and a list of printf() args just like syslog(3).
Establish an ISA relationship with base classes at compile time
Allows you to both load one or more modules, while setting up inheritance from those modules at the same time.
Module for sending mails with attachments through an SMTP server
Mail::Sender provides an object-oriented interface to sending mails. It directly connects to the mail server using IO::Socket.
Common Scalar and List utility subroutines
This package contains a selection of subroutines that people have expressed would be nice to have in the perl core, but the usage would not really be high enough to warrant the use of a keyword, and the size so small such that being individual extensions would be wasteful.
The Specio distribution provides classes for representing type constraints and coercion, along with syntax sugar for declaring them. Note that this is not a proper type system for Perl. Nothing in this distribution will magically make the Perl interpreter start checking a value's type on assignment to a variable. In fact, there's no built-in way to apply a type to a variable at all. Instead, you can explicitly check a value against a type, and optionally coerce values to that type.
When you import a function into a Perl package, it will naturally also be available as a method. The 'namespace::autoclean' pragma will remove all imported symbols at the end of the current package's compile cycle. Functions called in the package itself will still be bound by their name, but they won't show up as methods on your class or instances. This module is very similar to namespace::clean, except it will clean all imported functions, no matter if you imported them before or after you 'use'd the pragma. It will also not touch anything that looks like a method.
This package is the shared library for perl.
Various ancient mail-related perl modules
This is MailTools, a set of perl modules related to mail applications.
Implements default import method for modules
The Exporter module implements an import method which allows a module to export functions and variables to its users' name spaces. Many modules use Exporter rather than implementing their own import method because Exporter provides a highly flexible interface, with an implementation optimized for the common case.
Dispatches messages to one or more outputs
Log::Dispatch is a suite of OO modules for logging messages to multiple outputs, each of which can have a minimum and maximum log level. It is designed to be easily subclassed, both for creating a new dispatcher object and particularly for creating new outputs. An Apache output is available in perl-Log-Dispatch-ApacheLog package.
The functions exported by this module deal with runtime handling of Perl modules, which are normally handled at compile time. This module avoids using any other modules, so that it can be used in low-level infrastructure