Ports Search

This is a port of the glibc gnu regex engine into perl. There are few reasons you would need this. The few I can think of include: 0) You wish to use untrusted user expressions in such a way as to be able to catch errors. Example: eval { alarm 2; m/((){1024}){1024}/ } is an instant uncatchable segmentation fault. GNU's regexps will still fail, but in a timeout way rather than an instant segfault way. 1) You wish to have POSIX compliance on ... something ... Perl's regexps are slightly different -- arguably better, but different.

Petal is a XML based templating engine that is able to process any kind of XML, XHTML and HTML. Petal borrows a lot of good ideas from the Zope Page Templates TAL specification, it is very well suited for the creation of WYSIWYG XHTML editable templates. The idea is to further enforce the separation of logic from presentation. With Petal, graphic designers can use their favorite WYSIWYG editor to easily edit templates without having to worry about the loops and ifs which happen behind the scene.

This provides a simple interface to Plucene. Plucene is large and multi- featured, and it expected that users will subclass it, and tie all the pieces together to suit their own needs. Plucene::Simple is, therefore, just one way to use Plucene. It's not expected that it will do exactly what *you* want, but you can always use it as an example of how to build your own interface.

The Parse::FixedLength module facilitates the process of breaking a string into its fixed-length components. Sure, it's a glorified (and in some ways more limited) substitute for the perl functions pack and unpack, but it's the author's belief that this module helps in the maintainability of working with fixed length formats as the number of fields in a format grows.

POD::Abstract provides a means to load a POD (or POD compatible) document without direct reference to it's syntax, and perform manipulations on the abstract syntax tree. This can be used to support additional features for POD, to format output, to compile into alternative formats, etc. While Pod looks like a simple format, the specification calls for a number of special cases to be handled, and that makes any software that works on Pod as text more complex than it needs to be. In addition to this, Pod does not lend itself to a natural structured model. This makes it difficult to manipulate without damaging the validity of the document. Pod::Abstract solves these problems by loading the document into a structured tree, and providing consistent traversal, searching, manpulation and re-serialisation. Pod related utilities are easy to write using Pod::Abstract.

Pod::Autopod is designed to generate pod documentation of a perl class by analysing its code. The idea is to have something similar like javadoc. So it uses also comments written directly obove the method definitions. It is designed to asumes a pm file which represents a class. Of course it can not understand every kind of syntax, parameters, etc. But the plan is to improve this library in the future to understand more and more automatically.

SVG.pm is a perl extention to generate stand-alone or inline SVG (scaleable vector graphics) images using the W3C SVG xml recommendation.

Pod::Elemental is a system for treating a Pod (plain old documentation) documents as trees of elements. This model may be familiar from many other document systems, especially the HTML DOM. Pod::Elemental's document object model is much less sophisticated than the HTML DOM, but still makes a lot of document transformations easy.

POD is a pretty simple format to write, but it can be a big pain to deal with reading it and doing anything useful with it. Most existing POD parsers care about semantics, like whether a =item occurred after an =over but before a back, figuring out how to link a L<>, and other things like that. Pod::Eventual is much less ambitious and much more stupid. Fortunately, stupid is often better. (That's what I keep telling myself, anyway.) Pod::Eventual reads line-based input and produces events describing each POD paragraph or directive it finds. Once complete events are immediately passed to the handle_event method. This method should be implemented by Pod::Eventual subclasses. If it isn't, Pod::Eventual's own handle_event will be called, and will raise an exception.

Pod::HtmlEasy is a perl module to generate HTML data from POD in a easy and personalized mode. By default the HTML generated is similar to the CPAN site style for module documentation.