Results 631–640 of 1,719 for /textproc/.(0.003 seconds)
The Fastest Lexer in the West
Parse::Flex works similar to Parse::Lex, but it uses XS for faster
performance.
This module allows you to construct a lexer analyzer with your custom
rules. Parse::Flex is not intended to be used directly; instead, use the
script makelexer.pl to submit your grammar file. The output of the script
is a custom shared library and a custom .pm module which, among other
things, will transparently load the library and provide interface to your
(custom) lexer. In other words, you supply a grammar.l file to
makelexer.pl and you receive Flex01.pm and Flex02.so . Then, use only the
Flex01.pm - since Flex01.pm will automatically load Flex01.so.
The grammar.l file requires the same syntax as flex(1); that is, the
actions are written in C . See the flex(1) documentation to learn the
syntax, or fetch the sample t/grammar.l file inside this package.
Module for manipulating bibliographic records in the USMARC format
A Perl 5 module for reading in, manipulating, and outputting
bibliographic records in the USMARC format. It handles conversions
from MARC into ASCII (text), Library of Congress MARCMaker, HTML,
and ISBD. Input from MARCMaker format is also supported. Individual
records, fields, indicators, and subfields can be created, modified, and
deleted. It can extract URLs from the 856 field into HTML.
Parse phone numbers
Parse phone numbers. Phone number have a defined syntax (to a point), so
they can be parsed (to a point).
Perl5 routines that present a simple interface to parse syslog files
Parse::Syslog presents a simple interface to parse syslog
files: you create a parser on a file (with new) and call
next to get one line at a time with Unix-timestamp, host,
program, pid and text returned in a hash-reference.
Collection of handy Perl::Critic policies
Perl::Critic::Bangs is a collection of Perl::Critic policies
that will help make your code better.
A collection of Perl::Critic Policies
Perl::Critic::Itch was created to fulfill some special requests when analyzing
Perl Code. This policies, may not be useful to everyone, and surely not
consensual, but they solve some little itches I had, and it makes me sleep
better at night!
Policies for Perl::Critic concerned with using Moose
Some Perl::Critic policies that will help you keep your code in good shape with
regards to Moose.
Supplemental policies for Perl::Critic
This is a collection of Perl::Critic policies that are not included in the
Perl::Critic core for a variety of reasons:
Experimental
Some policies need some time to work out their kinks, test usability, or
gauge community interest. A subset of these will end up in the core
Perl::Critic someday.
Requires special dependencies
For example, some policies require development versions of PPI (or some
other CPAN module). These will likely end up in the Perl::Critic core when
their dependencies are fulfilled.
Peripheral to Perl
For example, the Editor::RequireEmacsFileVariables policy is metacode.
Also, the Miscellanea::RequireRcsKeywords policy pertains to the
development process, not the code itself. These are not part of
Perl::Critic's mission.
Special purpose
For example, policies like CodeLayout::RequireASCII designed to scratch
itches not felt by most of the community. These will always remain in a
Perl::Critic supplement instead of in the core.
some add-on perlcritic policies
This is a collection of add-on policies for Perl::Critic. They're under a
"pulp" theme plus other themes according to their purpose (see "POLICY THEMES"
in Perl::Critic).
A set of additional policies for Perl::Critic
Some Perl::Critic policies to make your code more clean.