Free command line parser software for linux

C++ Command Line Library provides a framework for handling command line options and arguments. Either variables (of any type) are set to values given at the command line. Or user defined functions are called with arguments (of any type) read from the command line.
It was developed and tested using kdevelop 2.1 and gcc 2.95.3 on SuSE Linux 7.3.x
Main features:
- Easy extraction of command line arguments
- Automatic conversion of command line arguments to any type (even user defined classes)
- Convenient handling of command line usage errors by exceptions
- Complete documentation
- And all this is absolutely free

MIME::Parser is a experimental class for parsing MIME streams.

SYNOPSIS

Before reading further, you should see MIME::Tools to make sure that you understand where this module fits into the grand scheme of things. Go on, do it now. Ill wait.
Ready? Ok...

Basic usage examples

### Create a new parser object:
my $parser = new MIME::Parser;

### Tell it where to put things:
$parser->output_under("/tmp");

### Parse an input filehandle:
$entity = $parser->parse(*STDIN);

### Congratulations: you now have a (possibly multipart) MIME entity!
$entity->dump_skeleton; # for debugging

Examples of input

### Parse from filehandles:
$entity = $parser->parse(*STDIN);
$entity = $parser->parse(IO::File->new("some command|");

### Parse from any object that supports getline() and read():
$entity = $parser->parse($myHandle);

### Parse an in-core MIME message:
$entity = $parser->parse_data($message);

### Parse an MIME message in a file:
$entity = $parser->parse_open("/some/file.msg");

### Parse an MIME message out of a pipeline:
$entity = $parser->parse_open("gunzip - < file.msg.gz |");

### Parse already-split input (as "deliver" would give it to you):
$entity = $parser->parse_two("msg.head", "msg.body");

Examples of output control

### Keep parsed message bodies in core (default outputs to disk):
$parser->output_to_core(1);

### Output each message body to a one-per-message directory:
$parser->output_under("/tmp");

### Output each message body to the same directory:
$parser->output_dir("/tmp");

### Change how nameless message-component files are named:
$parser->output_prefix("msg");

Examples of error recovery

### Normal mechanism:
eval { $entity = $parser->parse(*STDIN) };
if ($@) {
$results = $parser->results;
$decapitated = $parser->last_head; ### get last top-level head
}

### Ultra-tolerant mechanism:
$parser->ignore_errors(1);
$entity = eval { $parser->parse(*STDIN) };
$error = ($@ || $parser->last_error);

### Cleanup all files created by the parse:
eval { $entity = $parser->parse(*STDIN) };
...
$parser->filer->purge;

Examples of parser options

### Automatically attempt to RFC-1522-decode the MIME headers?
$parser->decode_headers(1); ### default is false

### Parse contained "message/rfc822" objects as nested MIME streams?
$parser->extract_nested_messages(0); ### default is true

### Look for uuencode in "text" messages, and extract it?
$parser->extract_uuencode(1); ### default is false

### Should we forgive normally-fatal errors?
$parser->ignore_errors(0); ### default is true
Miscellaneous examples
### Convert a Mail::Internet object to a MIME::Entity:
@lines = (@{$mail->header}, "n", @{$mail->body});
$entity = $parser->parse_data(@lines);

Command Line Content Management System is my own command line content management system. Its not a dynamic cms, but a script that takes a source tree and creates a web site out of it.
The idea came to me when i was using m4 for my website to generate the HTML, but i did not like the idea that i was still typing HTML in my pages, even if it was simplified by using macros. I was updating a wiki page somewhere when it hit me: i wanted a command line system that was able to take wiki style input for page content. The result is clcms.
Its in beta state at the moment, mostly to try out some different approaches to various
challenges. But i thought id share it now, so if youre interested and might have some ideas on where to go from here, drop me a line (or a patch). At least it can build this site and the tutorial site, but anything more fancy will probably not work.
Its also a way for me to learn Python, so i might in my ignorance produce some weird constructs here and there. Please let me know, but be gentle.
Main features:
- Updates should be possible with a terminal and an editor
- Content is stored in a directory tree
- Adding pages (or items?) should be as easy as creating a new file and typing some lines in it.
- For default pages/items no config necessary
- No HTML, XML or anything alike for normal usage
- All pages have their binary content (images, download files) in the directory of the page itself
- All output is static, no generating on the fly
Usage:
After untarring the tarball, add < dir>/bin to your path or copy bin/clcms.py to a directory in your path.
You can now go to < dir>/examples/documentation and build the tutorial by running
clcms.py
Now wasnt that easy?
Point your browser to file://< dir>/examples/documentation/out/index.html and see the result of all your hard work.
If it did not work, its not your fault. Just remember that version number.
Enhancements:
- .page files can now contain content attributes.
- Filename extensions are removed and replaced by attribute lines in .page files.
- The page.meta file should now be called page.attr.
- The nomenu option had disappeared in a previous release, and has been put back.

Randomize Lines (rl) is a command-line tool that reads lines from an input file or stdin, randomizes the lines and outputs a specified number of lines. It does this with only a single pass over the input while trying to use as little memory as possible.
I wrote rl in my spare time mainly to be able to select a random audio file to play when my toast is done (script in combination with find and sleep). Another reason was to familiarize myself with autoconf and friends.
The most recent version of this page can be found at http://ch.tudelft.nl/~arthur/rl/.
Warning: rl is software in development. The command line options and default behavior may change between releases.
Another Warning: I have mostly lost interest in this project and am not planning on doing much development on it any more. I will however still accept patches and fix important bugs (this more or less contradicts the previous warning).
Enhancements:
- A dangerous example was removed from the manual page and was replaced by several benign ones.

Arg_parser is an argument parser that follows POSIX and GNU conventions for command line arguments. Arg_parser is implemented as a C++ class, and is simpler, easier to use, and safer that "getopt_long".
Arg_parser does not modify its arguments, nor uses any global variables. So you may create more than one parser in your program if you need or want to. Arg_parser can also parse options from configuration files.
To use Arg_parser in your own programs simply copy the files "arg_parser.h" and "arg_parser.cc" in your sorce tree. See also the file "main.cc" for an example of use.
Enhancements:
- The license has been updated to GPL version 3 or later.

Biblio::Document::Parser Perl module is a document parsing framework.

Biblio::Document::Parser provides generic methods that should be overriden by specific parsers. This class should not be used directly, but rather be overridden by specific parsers. Parsers that extend the Document::Parser class should at least override the parse method.

METHODS

$docparser = Biblio::Document::Parser->new()

The new() method creates a new parser instance.

@references = $parser->parse($lines, %options)

The parse() method takes either a content string or an IO::Handle, and returns an array of reference strings.

Bigtop::Parser is the Parse::RecDescent grammar driven parser for bigtop files.

SYNOPSIS

Make a file like this:
config {
base_dir `/home/username`;
Type1 Backend {}
Type2 Backend {}
Type3 Backend {}
}
app App::Name {
table name { }
controller SomeController {}
}
Then run this command:
bigtop my.bigtop all

This module is really only designed to be used by bigtop. It provides the grammar which understands bigtop files and turns them into syntax trees. It provides various utility functions for bigtop (or similar tools you might write) and for backends.

Reading further is an indication that you are interested in working on Bigtop and not just in using it to serve your needs.