Automated program and text generation.
'AutoGen' generates program files that contain repetitive text with varied substitutions. It simplifies the maintenance of programs with large amounts of repetitive text, which is useful if several blocks of such text must be synchronized. It includes:
- AutoOpts - automates the handling of command line, environment and config file options, including usage text, man pages, and the invoking section of an info doc
- getdefs - extracts AutoGen definitions from stylized comments embedded in source code
- columns - tabularizes lists for improved output appearance
- AutoXDR - NFSv4 specifies that its remote procedure calls be batched. AutoGen generates the code for marshalling and unmarshalling the arguments on both sides of the RPC request
- AutoFSM - produces a transition table and prototype finite state machine where it is possible to determine a state transition type (token code) without reference to the current state
- xml2ag - lets AutoGen use any XML file as if it were a set of AutoGen definitions
This is a GNU package:
26 July 2010
Leaders and contributors
Resources and communication
|VCS Repository Webview||https://git.savannah.gnu.org/cgit/autogen.git/|
|VCS Repository Webview||https://cvs.savannah.gnu.org/viewvc/autogen/|
|VCS Repository Webview||https://web.cvs.savannah.gnu.org/viewvc/autogen/|
|Source requirement||POSIX environment|
|Source requirement||Bourne-like shell|
|Required to build||ANSI C|
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.