Ansiprint is a utility for printing text files (or stdin) from remote terminals using ANSI telnet escape sequences. It was inspired by the ansiprt.c component of the University of Washington's excellent email package, PINE. However, since the author believed that ansiprt.c was released under "somewhat ridiculous terms", ansiprint has been completely re-written in C++, and includes a variety of new features.
NFSv4 specifies that the RPC calls be batched into a "compound" call. There is no support for this in RPCGEN. By rearranging the ONC IDL for NFSv4 into AutoGen definitions, these templates will emit the original IDL *plus* all the code to package, send, distribute, collect, return, and dispatch the results. The distributed program author merely needs to call and supply server procedures for the routines specified in the IDL. Templates for these calls and service routines is provided, too. The NFSv4 definitions are included.
clo++ is a command line option parser generator. Given an XML file that contains a description of your program and its options, clo++ can generate code to parse its command line. In addition to code generation, clo++ can also generate man pages. Other languages and output formats can easily be added because clo++ generates its output using templates.
This is a PHP class that attempts to validate a given e-mail address at three levels: matching the address against a RFC compliant regular expression, verifing the existence of the destination SMTP server by verifying the respective DNS MX record, and connecting to that server to see if the given address is accepted as a valid recipient. The class also features a debugging output option that lets you see the remote SMTP server connection and data exchange dialog to see the real cause why an apparently valid address may not be accepting messages.
Ficl (Forth inspired command language) is an ANS Forth interpreter written in C. Unlike traditional Forths, this interpreter is designed to be embedded into other systems as a command/macro/development prototype language. Ficl provides object extensions that can be used to wrap methods and structures of the host system without altering them.
FreeMarker is a template engine that was originally designed so that servlet-based applications could keep graphical design separate from application logic. The templates provide an easy and highly flexible way to generate any kind of text output (HTML, PostScript, TeX, source code, etc.) from a variety of data sources such as Java objects, Jython objects, XML object models, and more.
HappyDoc is a tool for extracting documentation from Python source code. It differs from other such applications by the fact that it uses the parse tree for a module to derive the information used in its output instead of importing the module directly. This allows the user to generate documentation for modules which need special context to be imported.
ICCLIB implements support for reading and writing of color profile files that conform to the International Color Consortium (ICC) Profile Format Specification, Version 3.4. The ICC Profile Format is a cross-platform device profile format that can be used to translate color data created on one device into another device's native color space. See the profile specification at color.org. In summary ICCLIB provides support for all version 3.4 header elements, Tags, and Tag Types, conversion to/from machine native representation of all data types, user-defined Tags, adding/deleting Tags, Tag type sharing within a file (often used for sharing LUTs amongst intents), reading/writing embedded profiles, a single function for transforming color values through a profile (including support for intents, forward and reverse transforms, gamut lookup or preview lookup), support and code examples for creating all profile types, monochrome, matrix, and Lut, and it loads Tag Types on demand to conserve memory space.
IDebug is an advanced debugging framework for Java. It provides the standard core debugging and specification constructs such as assertions, debug levels and categories, stack traces, and specialized exceptions. Debugging functionality can be fine-tuned to a per-thread and/or a per-class basis, debugging contexts can be stored and recovered from persistent store, and several aspects of the debugging run-time are configurable at the meta-level.