4D generates true machine-level code for the target processor. This results in applications that execute at the fastest possible speed. 4D Compiler checks your syntax as it compiles and ensures that your compiled application is free of syntax errors.
You can merge your compiled database with 4D Engine and create a standalone executable application. On Mac OS, 4D Compiler merges 4D Engine and the compiled database application into a single, double-clickable application. On Windows, the compiler generates three files: DatabaseName.EXE, DatabaseName.4DC, and DatabaseName.RSR. The resulting application icon can be customised to give your application a polished look and feel.
This option generates a text file containing a list of errors and warnings detected during the compilation process. 4D can open this file directly and use it for interactive debugging and error correction. The error file may also include additional warnings that assist the programmer in locating potential software bugs.
4D Compiler generates a text file containing information about all database objects, their data types. The symbol table also includes a complete list of your methods and functions, the data types of their parameters and, for functions, the data type of the value returned. The symbol table allows the programmer to optimise use of database variables to reduce memory requirements, optimise certain operations, and locate potential application bugs.
Range Checking provides a particularly powerful set of diagnostics used during testing and debugging. A database application that is compiled with Range Checking includes code that will check memory and variable access dynamically during the execution of your compiled code. Range checking errors are reported to the user with specific information relating to the type of error, method where the error occurred, and the line number of the error. The programmer can then use this information to fix bugs in the code that might not have been otherwise found during normal testing procedures.
Windows
Pentium II minimum
800 X 600 monitor resolution
Windows 2000, Windows XP.
256 MB RAM minimum
MacOS:
G3 or better processor
800 X 600 monitor resolution
Mac OS X v10.2.8 or later
256 MB RAM minimum