Ports Search

Workflow - Simple, flexible perl-based system to implement workflows

XML-Compile-Tester support XML::Compile related regression testing.

Java has Castor, and now Perl has XML::Pastor! If you know what Castor does in the Java world, then XML::Pastor should be familiar to you. If you have a W3C XSD schema, you can generate Perl classes with roundtrip XML bindings.

This way of associating structs with Perl space objects is designed to supercede Perl's builtin T_PTROBJ with something that is designed to be: Extensible - The association of the pointer using sv_magicext can be done on any data type, so you can associate C structs with any representation type. - This means that you can add pointers to any object (hand coded, Moose or otherwise), while still having instance data in regular hashes. Opaque - The C pointer is neither visible nor modifiable from Perl space. - This prevents accidental corruption which could lead to segfaults using T_PTROBJ (e.g. $$ptr_obj = 0).

Cppcheck is a tool for static C/C++ code analysis, and it tries to detect bugs that your compiler do not see. Checks for: memory leaks, mismatching allocation-deallocation, buffer overrun, and many more. Cppcheck is versatile. You can check non-standard code that includes various compiler extensions, inline assembly code, etc. The goal is no false positives.

Xporter provides EXPORT functionality similar to Exporter with some different rules to simplify common cases. The primary difference, in Xporter is that the default EXPORT list remains the default EXPORT list unless the user specifically asks for it to not be included, whereas in Exporter, asking for any additional exports from the EXPORT_OK list, clears the default EXPORT list. Xporter makes it easy to reset or clear the default so that choice is left to the user. To reset the default EXPORT list to empty, a bare minus ('-') or logical-not sign ('!') is placed as the first parameter in the client's import list.

YAML::AppConfig extends the work done in Config::YAML and YAML::ConfigFile to allow more flexiable configuration files. Your configuration is stored in YAML and then parsed and presented to you via YAML::AppConfig. Settings can be referenced using get and set methods and settings can refer to one another by using variables of the form $foo, much in the style of AppConfig.

For Perl 6 we've been promised a "yada yada yada" operator, which makes '...' valid syntax for "I'll fill this bit in later.", allowing the code to compile, but issue a run-time warning. But, like many of the other things that may or may not happen in Perl 6, we can already make this happen in Perl 5. All you need is to 'use Yada::Yada::Yada' and off you go ...

A ZConf backed method of choosing a backend for a Perl module that has multiple backends. zcgui-get Gets the current preferred backends for a module. zcgui-gux Gets the value for useX. zcgui-la Lists available GUI backends for a ZConf::GUI compliant module. zcgui-lm Lists the modules that currently have preferences set. zcgui-set Set the preferred backends for a module. zcgui-sux Set the useX value for a module. zcgui-which Prints a list of the available preferred modules for a module.

This module was created as an alternative to use fields, and uses Class::Accessor::Fast as a base Creates accessors at compiletime Have own default new method: it creates object as a blessed hash, then locks keys to defined field list, and invoke init. So, recommended usage inside packages, is access by hash keys (it's 3 times faster then accessor). Since keys are locked, you will not suffer from autovivification. Public interface recommended to be documented as accessors. Uses Class::C3