4tH is a Forth compiler with a little difference. Instead of the standard Forth engine it features a conventional compiler. 4tH is a very small compiler that can create bytecode, C-embeddable bytecode, standalone executables, but also works fine as a scripting language. It supports about 95% of the ANS Forth CORE wordset and features conditional compilation, pipes, files, assertions, forward declarations, enumerations, structures, suspended execution, recursion, include files, etc. It comes with an RPN calculator, line editor, preprocessor, compiler, decompiler, C-source generator, a virtual machine, and a multitasking environment.
ATG Dynamo integration for JBuilder is a JBuilder 5 plugin that makes it easy to deploy J2EE applications to the ATG Dynamo Application Server version 5.1 (DAS). It can be installed and run with the other JBuilder 5 plugins such as BEA WebLogicServer 5.1, BEA WLS 6, IBM WebSphere 3.5, Borland AS 4.5, etc.
'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).
Aubit 4GL compiler is a programming language based on (and compatible with) Informix-4GL. It provides an easy way to generate screen/form based programs, since statements for handling Windows, Forms, Menus, SQL, and similar are built-in. With support for SQL statements forming an intrinsic part of the language, it's especially suitable for developing database-oriented applications. Database connectivity is provided for PostgreSQL, MySQL, Informix, and others via ODBC. It supports both ncurses (console mode) and GTK+ (GUI mode) output.
AutoCMS is a smaller CMS with the minimum needed to have a presence on the Internet. Its main file is less than 10kb large by default. No database is required. It only has the concept of one user (the admin). The password is protected with SHA1. CSS styles are easy to build and to change. Changing a page is very fast. XHTML and CSS code are validated by W3C validators. Data is stored in a PHP file which can be downloaded by FTP for backups. The generated contents are friendly for searchers. The result is visualized correctly in all browsers. It allows you to update all contents without having knowledge of programming.
Azzyzt JEE Tools is a set of Eclipse plugins for creating a so-called "azzyzted" project, and for creating code from a model. Azzyzt uses Java JPA entities as a model, and from that model it creates an enterprise application, ready to be deployed in a Java EE 6 application server like GlassFish 3.1, ready to be accessed via CORBA, SOAP, and REST. Thus the generated application is a set of Web services, providing all that you need in a typical CRUD application. Generated enterprise applications have separate source folders for generated and developer-supplied content. You can add your own functionality to a well-engineered base project. Azzyzt JEE Tools is not about user interfaces. It is expected that the generated application is accessed by a RIA frontend or by a fat client.
The program bisonc++ creates a C++ parser function and class having a cleaner setup than the code generated by Alain Coetmeur's bison++. Furthermore, since bisonc++ more closely follows current-day ideas about C++ programming, its code is easier to read. It expands the concepts initially implemented in bison and bison++, offering a cleaner setup of the generated parser class. The parser class is derived from a base-class, mainly containing the parser's token and type definitions, as well as several member functions that should not be (re)defined by the programmer.
Build Interceptor captures the .i files of any project while it is built from source using the gcc toolchain. Anyone who has tried this on a large scale will find out that it is non-trivial to build a project from source and obtain the .i files generated during the build process. Step-by-step instructions are given on how to use the provided scripts to do this without any modification to the build process of the project you are trying to capture. These scripts were used to capture the build process of 92.5% of the projects in the Red Hat Linux 7.3 distribution.