The gettext lint tools is a collection of tools for checking the validity and
consistency of PO and POT files. It also includes an experimental glossary
building tool.
This package includes:
* POFileStatus - PO file validator and status reporting
* POFileChecker - searches for common mistakes in PO files
* POTFileChecker - searches for common mistakes in POT files
* POFileConsistency - PO file consistency checks
* POFileConsistencyShell - PO file consistency checks, interactive mode
* POFileEquiv - PO file glossary generator
All tools generate XML to the standard output; just run them with a list of PO
or POT files to check. Some have extra options, run the command with no
parameters for a short usage message.
Gradle is build automation evolved.
Gradle can automate the building, testing, publishing, deployment
and more of software packages or other types of projects such as
generated static websites, generated documentation or indeed anything
else.
Gradle combines the power and flexibility of Ant with the dependency
management and conventions of Maven into a more effective way to
build. Powered by a Groovy DSL and packed with innovation, Gradle
provides a declarative way to describe all kinds of builds through
sensible defaults. Gradle is quickly becoming the build system of
choice for many open source projects, leading edge enterprises and
legacy automation challenges.
An abstract interface to highly-parameterizable queues/deques. Background:
There exists a feature space for queues that extends between:
* simple, single-ended, non-concurrent, bounded queues
* double-ended, threadsafe, growable queues
... with important points inbetween (such as the queues used for
work-stealing). This package includes an interface for Deques that
allows the programmer to use a single API for all of the above, while
using the type-system to select an efficient implementation given the
requirements (using type families). This package also includes a simple
reference implementation based on 'IORef' and "Data.Sequence".
An efficient packed, immutable Unicode text type (both strict and lazy),
with a powerful loop fusion optimization framework.
The Text type represents Unicode character strings, in a time and
space-efficient manner. This package provides text processing
capabilities that are optimized for performance critical use, both in
terms of large data quantities and high speed.
The Text type provides character-encoding, type-safe case conversion via
whole-string case conversion functions. It also provides a range of
functions for converting Text values to and from ByteStrings, using
several standard encodings.
Efficient locale-sensitive support for text IO is also supported.
The Netwide Assembler (NASM) is an x86 and amd64 (x86-64) assembler designed
for portability and modularity. It will output flat-form binary files, a.out
(Linux and *BSD), COFF, ELF32, ELF64, Mach-O, Microsoft OMF (OBJ), Win32,
Win64, as86 (Minix/Linux bin86 v0.3), LADsoft IEEE-695, Intel hex, Motorola
S-record, and a home-grown format called RDOFF. NASM syntax is similar to
Intel's, but is less complex. It supports Pentium, P6, MMX, 3DNow!, SSE,
SSE2, SSE3, SSE4.1, SSE4.2, XOP/FMA4/CVT16 (rev 3.03), and x64 opcodes, among
others. It has strong support for macro conventions.
The port also includes NDISASM, a binary file disassembler which uses the
same instruction set as NASM.
Algorithm::Accounting provide simple aggregation method to make log
accounting easier. It accepts data in rows, each rows can have many
fields, and each field is a scalar or a list(arrayref).
The basic usage is you walk through all your logs, and use append_data()
to insert each rows, (you'll have to split the line into fields), and
then call result() to retrieve the result, or report() to immediately
see simple result.
You may specify a filed_groups parameter (arrayref of arrayref), and
Algorithm::Accounting will account these fields in groups.
CHI provides a unified caching API, designed to assist a developer in
persisting data for a specified period of time.
The CHI interface is implemented by driver classes that support
fetching, storing and clearing of data. Driver classes exist or will
exist for the gamut of storage backends available to Perl, such as
memory, plain files, memory mapped files, memcached, and DBI.
CHI is intended as an evolution of DeWitt Clinton's Cache::Cache
package, adhering to the basic Cache API but adding new features and
addressing limitations in the Cache::Cache implementation.
AUnit is a set of Ada packages based on the xUnit family of unit test
frameworks. It is intended as a developer's tool to facilitate confident
writing and evolution of Ada software. It is purposely lightweight, as
one of its main goals is to make it easy to develop and run unit tests,
rather than to generate artifacts for process management. The framework
supports easy composition of sets of unit tests to provide flexibility
in determining what tests to run for a given purpose.
This is the legacy 2.13 version of autoconf. It is explicitly for use with
older software packages that are not buildable with the current autoconf.
Autoconf is an extensible package of m4 macros that produce shell
scripts to automatically configure software source code packages.
These scripts can adapt the packages to many kinds of UNIX-like
systems without manual user intervention. Autoconf creates a
configuration script for a package from a template file that lists the
operating system features that the package can use, in the form of m4
macro calls.
DateTime::Calendar::Hebrew is the implementation of the Hebrew calendar. Read
on for more details on the Hebrew calendar.
The Hebrew/Jewish calendar is a Luni-Solar calendar. Torah Law mandates that
months are Lunar. The first day of a month coincides with the new moon in
Jerusalem. (In ancient times, this was determined by witnesses. Read the books
in the bibliography for more info). The Torah also mandates that certain
holidays must occur in certain seasons. Seasons are solar, so a calendar that
can work with lunar & solar events is needed.