Inline::TT provides Inline access to version 2.0 and higher of the Template
Toolkit. This allows you to house your templates inside the source code file,
while retaining the ability to cache compiled templates on the disk (via
Inline's caching mechanism).
The names of the blocks in the template are exported as functions. Call these
with a reference to a hash of values, which will be used for interpolation in
the templates. This hash reference is the same as the second argument to the
process method of any Template object. The output from template toolkit will be
returned to you as a single string. Note that leading and trailing spaces are
trimmed, further the template toolkit options PRE_CHOMP and POST_CHOMP are set.
Currently, there is no way to change these behaviors.
This module is a simple wrapper around Locale::Maketext::Lexicon,
designed to alleviate the need of creating Language Classes for module
authors.
If Locale::Maketext::Lexicon is not present, it implements a minimal
localization function, so the program can function normally.
The Inline::Tcl module allows you to put Tcl source code directly
"inline" in a Perl script or module. A Tcl interpreter is loaded and the
Tcl code is interpreted, then Perl asks the Tcl interpreter which global
procedures have been defined. Those functions are made available to your
Perl program as if they had been written in Perl.
The process of interrogating the Tcl interpreter for globals only occurs
the first time you run your Tcl code. The namespace is cached, and
subsequent calls use the cached version.
The Inline module allows you to put source code from other programming
languages directly "inline" in a Perl script or module. The code is
automatically compiled as needed, and then loaded for immediate access
from Perl.
Inline saves you from the hassle of having to write and compile your own
glue code using facilities like XS or SWIG. Simply type the code where
you want it and run your Perl as normal. All the hairy details are
handled for you. The compilation and installation of your code chunks
all happen transparently; all you will notice is the delay of
compilation on the first run.
The Inline code only gets compiled the first time you run it (or
whenever it is modified) so you only take the performance hit once. Code
that is Inlined into distributed modules (like on the CPAN) will get
compiled when the module is installed, so the end user will never notice
the compilation time.
This module does the same thing as msgfmt from GNU gettext-tools,
except this is pure Perl.
InlineX::C2XS - create an XS file from an Inline C file.
The C file that InlineX::C2XS needs to find would contain
only the C code.
InlineX::C2XS looks for the file in ./src directory - expecting that the
filename will be the same as what appears after the final '::' in the
module name (with a '.c' extension). ie if the module is called
My::Next::Mod it looks for a file ./src/Mod.c, and creates a file
named Mod.xs. Also created, is the file 'INLINE.h' - but only if that
file is needed. The generated xs file (and INLINE.h) will be written
to the cwd unless a third argument (specifying a valid directory) is
provided to the c2xs() function.
The created XS file, when packaged with the '.pm' file, an
appropriate 'Makefile.PL', and 'INLINE.h' (if it's needed),
can be used to build the module in the usual way - without
any dependence upon the Inline::C module.
InlineX::CPP2XS is a perl module to create an XS file from an
Inline C++ file.
Data validator. Validates only the data. No form generation, no javascript
generation, no other stuff that does something else. Only data validation!
Features:
* Validates data that is presented as a hash reference
* Multiple values
* Field registration
* Group validation
* Conditional validation
Iodef::Pb::Simple is a Perl extension providing high level API access to
Iodef::Pb, which is useful to an array of IODEF protocol buffer objects
into things like tab-delimited tables, csv, and snort rules.
The LockFile::Simple extension provides simple file locking, of
the advisory kind, i.e. it requires cooperation between applications
wishing to lock the same files.
It is meant to be used in quick-and-dirty scripts or more elaborated
programs that want a simple locking scheme, yet with a reasonable
level of configuration.