ANTLR (ANother Tool for Language Recognition) is a language tool that provides a framework for constructing recognizers, compilers, and translators from grammatical descriptions containing C++, Java, or Sather actions. It is similar to the popular compiler generator YACC, however ANTLR is much more powerful and easy to use. ANTLR-produced parsers are not only highly efficient, but are both human-readable and human-debuggable (especially with the interactive ParseView debugging tool). ANTLR can generate parsers, lexers, and tree-parsers in either C++, Java, or Sather. ANTLR is currently written in Java.
'App' is a preprocessor for C++ that accepts as input arbitrary C++ code that may contain embedded constructs for specifying algebraic data types and associated pattern matching operations, and produces as output the same code with all such constructs translated to normal C++. What app essentially does is provide for C++ pretty much the same capabilities that functional languages have regarding algebraic types. 'Applib' is the associated runtime library that supports the core run time requirements of the translated code, and which provides additional utilities (applib is covered by the LGPL).
AutoGen is a tool designed for generating program files that contain repetitive text with varied substitutions. Its goal is to simplify the maintenance of programs that contain large amounts of repetitious text. This is especially valuable if there are several blocks of such text that must be kept synchronized. Output is specified with a Scheme-enhanced output template. Input, if required by your template, may come from AutoGen definitions, CGI data, or XML files.
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.
AutoOpts is an integrated part of AutoGen. Based on a very simple option description file, it will process configuration files, environment variables, command line options, text strings passed by client programs, and will make the results easily accessible to the client program. It will also produce a man page and the info-doc invoking section automatically.
Builder Xcessory PRO for Linux is the industry's most advanced graphical user interface builder for Motif. BX PRO provides a comprehensive visual reuse environment that speeds development of mission-critical applications. BX PRO integrates three best-of-breed tools to create an unparalleled application development suite.
Clig uses a simple description file to create C-code to interprete the typical *NIX command line as well as an up-to-date usage-message and a manual page skeleton. It supports Flag, String, Int, Long, Float and Double types, with ranges, defaults, and more. The generated C-Code is ANSI but has been reported to work with C++. It is self contained code which does not depend on any library other than libc. Included is a TCL-only TCL-package to instrument your TCL scripts the same way as your C-programs.
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.
gitty-gitty, the (general | GNU) template generation tools, are a set of scripts for creating a whole set of sources which may already be compiled and installed using the GNU development tools. Think of gtgt as a program which is able to create an already compilable, very sophisticated "hello world" program, written in C or C++ and constituted by a main program, two internal modules (classes), and one static and one shared library, and this complex "Hello World" is already fully embedded into the GNU autoconf/automake development environment. By using gitty-gitty, you will get a template of sources for the main cases you might meet, and which you can also use as examples for automake, autoconf, etc.