perlbrew is a program to automate the building and installation of perl in an
easy way. It provides multiple isolated perl environments, and a mechanism for
you to switch between them.
Everything are installed unter ~/perl5/perlbrew. You then need to include a
bashrc/cshrc provided by perlbrew to tweak the PATH for you. You then can
benefit from not having to run 'sudo' commands to install cpan modules because
those are installed inside your HOME too.
For the documentation of perlbrew usage see perlbrew command on CPAN, or by
running perlbrew help. The following documentation features the API of
App::perlbrew module, and may not be remotely close to what your want to read.
The Class:Multimethod module exports a subroutine (&multimethod) that can
be used to declare other subroutines that are dispatched using a algorithm
different from the normal Perl subroutine or method dispatch mechanism.
Normal Perl subroutines are dispatched by finding the appropriately-named
subroutine in the current (or specified) package and calling that. Normal
Perl methods are dispatched by attempting to find the appropriately-named
subroutine in the package into which the invoking object is blessed or,
failing that, recursively searching for it in the packages listed in the
appropriate @ISA arrays.
Class::Multimethods multimethods are dispatched quite differently. The
dispatch mechanism looks at the classes or types of each argument to the
multimethod (by calling ref on each) and determines the "closest" matching
variant of the multimethod, according to the argument types specified in
the variants' definitions (see "Finding the "nearest" multimethod" for a
definition of "closest").
The Devel::Required module only serves a purpose in the development
environment of an author of a CPAN module (or more precisely: a user of the
ExtUtils::MakeMaker module). It makes sure that any changes to the required
modules specified in the Makefile.PL are automatically reflected in the
appropriate text file and in the appropriate source files (either
explicitly or implicitly specified).
It takes the information given with the PREREQ_PM parameter and by default
writes this to the README file, as well as to the POD of the file specified
with the VERSION_FROM parameter. Both these defaults can be overridden with
the "text" and "pod" parameters in the use Devel::Required specification.
HTML_Template_IT:
Simple template API.
The Isotemplate API is somewhat tricky for a beginner although it is the best
one you can build. template::parse() [phplib template = Isotemplate] requests
you to name a source and a target where the current block gets parsed into.
Source and target can be block names or even handler names.
Features :
* Nested blocks
* Include external file
* Custom tags format (default {mytag})
HTML_Template_ITX :
With this class you get the full power of the phplib template class.
You may have one file with blocks in it but you have as well one main file
and multiple files one for each block. This is quite useful when you have
user configurable websites. Using blocks not in the main template allows
you to modify some parts of your layout easily.
Haskell bindings to the International Components for Unicode (ICU)
libraries. These libraries provide robust and full-featured Unicode
services on a wide variety of platforms.
Features include:
* Both pure and impure bindings, to allow for fine control over efficiency
and ease of use.
* Breaking of strings on character, word, sentence, and line boundaries.
* Access to the Unicode Character Database (UCD) of character metadata.
* String collation functions, for locales where the conventions for
lexicographic ordering differ from the simple numeric ordering of
character codes.
* Character set conversion functions, allowing conversion between Unicode
and over 220 character encodings.
* Unicode normalization. (When implementations keep strings in a normalized
form, they can be assured that equivalent strings have a unique binary
representation.)
* Regular expression search and replace.
sysconftool is a development utility that helps to install application
configuration files. sysconftool allows an existing application to be
upgraded without losing the older version's configuration settings.
sysconftool is a script that is used by applications to update configuration
files when a new version of the application is installed. sysconftool reads
the new application configuration files, reads any older versions of those
files that are already installed, then replaces the old versions with the
new ones, but preserving any custom changes contained in the old versions.
For more information on sysconftool, and why applications need it, see
the installed manual pages: sysconftool(1) and sysconftool(7). With most
versions of the man command: "man 1 sysconftool" and "man 7 sysconftool".
IRONSIDES is an authoritative DNS server that is provably invulnerable to
many of the problems that plague other servers. It achieves this property
through the use of formal methods in its design, in particular the language
Ada and the SPARK formal methods tool set. Code validated in this way is
provably exception-free, contains no data flow errors, and terminates only
in the ways that its programmers explicitly say that it can. These are very
desirable properties from a computer security perspective.
IRONSIDES is not a complete implementation of DNS. In particular, it does
not support zone transfers or recursive queries. It does, however, support
a sufficient number of DNS records to be useful as an authoritative DNS
server for an enterprise.
HT is a file editor/viewer/analyzer for executables. The goal is to combine
the low-level functionality of a debugger and the usability of IDEs. We aim
towards a perfect hex-editing ability and support of the most important file
formats.
Support means that HT will be able to correctly display and modify the
executable header, image and other extensions specific to the file (import/
export sections, relocations, debugging information etc.). Support will
probably include the following file formats:
- Win32 portable executables (PE) (good support)
- Unix executable and linkable format (ELF) (good support)
- DOS standard executables (MZ) (supported)
- Win32 linear executables (LE) (supported)
- Windows/OS2 "new" executables (NE) (supported)
- Unix common object file format (COFF) + DJGPP COFF (supported)
- OS2 linear executables (LX)
- Microsoft object files (.obj)
This port allows to access CP/M file systems similar to the well-known mtools
package, which accesses MSDOS file systems. It contains the followin set of
tools:
* cpmls - list sorted directory with output similar to ls, DIR, P2DOS DIR
and CP/M3 DIR[FULL]
* cpmcp - copy files from and to CP/M file systems
* cpmrm - erase files from CP/M file systems
* cpmchmod - change file permissions
* cpmchattr - change file attributes
* mkfs.cpm - make a CP/M file system
* fsck.cpm - check and repair a CP/M file system (only simple errors can
be repaired so far). Some images of broken file systems are provided.
* fsed.cpm - view CP/M file system
* manual pages for everything including the CP/M file system format
All CP/M file system features are supported. Password protection is ignored,
but a pseudo file [passwd] contains them decrypted.
LIBDSK is a library for accessing disks and disk image files.
It is intended for use in:
* Allows CPMTOOLS use of emulator .DSK images.
* Emulator tools - converting between real floppy disks and disk images,
as CPCTRANS / PCWTRANS do under DOS.
* Floppy controller emulation backend
* Data transfer from/to real CP/M systems via serial line.
LIBDSK has drivers for:
Raw files (including /dev/fdn), .DSK files (CPCEMU, JOYCE and other
Sinclair/Amstrad emulators), MYZ80 hard drive image, NanoWasp floppy image,
.CFI (Compressed Floppy Image, as created by FDCOPY.COM under DOS),
Linux floppy drive (supports CPC System and Data formats, which the standard
"Raw file" driver does not), Windows 3.x/95/98/ME/NT/2000 floppy drive,
DOS floppy drive (via the PC BIOS), CopyQM files (read-only),
TeleDisk files (read-only), APRIDISK image files,
rcpmfs - makes a Unix/Windows directory appear to be a CP/M disc image.