You can compile your projects, i.e., translate all of your methods into machine language. Compiling a project lets you check the consistency of the code and accelerate its execution, as well as making it possible to obfuscate the code in its entirety. Compilation is an indispensable step between the development of projects using 4D and their deployment as stand-alone applications.
The compilation is handled from your 4D application and is entirely automatic.
On macOS, the compilation requires that you install
Xcode. See this section for more information about this requirement.
Open the compiler window by selecting the Compiler... command in the Design menu or the Compiler toolbar button.
You can also launch directly the compilation by selecting the Start Compilation menu item from the Design menu.
- Click the Compile button to launch the compilation using the current compilation settings.
If no errors are detected, the actual compilation begins and the "Compilation successful" message is displayed at the bottom of the window when the compilation is completed:
You can immediately run your application in compiled mode and see how faster it is.
If errors are detected, the process is stopped and the "Compilation failed" message is displayed. The information area of the window displays the method names and line numbers concerned in a hierarchical list:
Double-click on each error detected to open the method or class concerned directly in the 4D method editor. The line containing the error is highlighted and the type of error is displayed in the syntax area of the window.
Use the Previous Error / Next Error commands of the Method menu to navigate from one error to the next.
The number of errors found during your first compilations may be daunting, but do not let this put you off. You will soon discover that they often spring from the same source, i.e., non-compliance with certain project conventions. The compiler always provides a precise diagnosis of the errors in order to help you correct them.
Compilation requires an appropriate license. Without this license, it is not possible to carry out a compilation (buttons are disabled). Nevertheless, it is still possible to check the syntax and generate Typing methods.
Once a project is compiled, it is possible to switch from interpreted mode to compiled mode, and vice versa, at any time and without having to quit the 4D application (except when the interpreted code has been removed). To do this, use tge Restart Interpreted and Restart Compiled commands of the Run menu. The Open project dialog box also offers a choice between interpreted or compiled mode for database startup.
When you switch from one mode to the other, 4D closes the current mode and opens the new one. This is equivalent to exiting and reopening the application. Each time you change from one mode to another, 4D executes the two following database methods (if specified) in this order:
On Exit ->
If you modify your project in interpreted mode, you must recompile it in order to have your edits taken into account in compiled mode.
Compiler window features
In addition to the Compile button, the Compiler window provides additional features that are useful during the project development phase.
The Check Syntax button starts the execution of the syntax-checking phase. At the end of the checking process, any errors detected are listed in the information area. You can double–click on an error line in order to display the corresponding method.
Syntax checking can also be launched directly using the Check Syntax command associated with the Compiler toolbar button. This option is the only one available if you do not have a suitable license to allow the compilation of applications.
The Generate Typing button creates or updates typing compiler methods. Compiler methods are project methods that group together all the variable and array typing declarations (process and interprocess), as well as the method parameters. These methods, when they exist, are used directly by the compiler during code compilation, resulting in faster compilation times.
The name of these methods must begin with
Compiler_. You can set the default name for each of the 5 compiler methods in the compiler settings window. The compiler methods that are generated and maintained by 4D automatically have the
Only the necessary compiler methods (i.e., those for which items already exist in the project) are generated.
The information area indicates any errors found during method creation or updating. Double-clicking on an error line causes the method and line concerned to be displayed in the Method editor.
Clear compiled code
The Clear compiled code button deletes the compiled code of the project. When you click on it, all of the code generated during compilation is deleted, the Restart Compiled command of the Run menu is disabled and the "Compiled Project" option is not available at startup.
Warnings are specific messages generated by the compiler when it checks the syntax. These messages are intended to draw your attention to statements that might lead to execution errors. They do not prevent compilation.
Depending on circumstances and the programming style used, these warnings may be more or less relevant. You can toggle the warnings on or off by clicking the Show/Hide Warnings button:
When this option is checked, the warnings (if any) are displayed in the window, after the other error types. They appear in italics:
Double-clicking a warning opens the corresponding method.
Disabling warnings during compilation
You can selectively disable certain warnings during compilation by inserting the following into the code of a 4D method:
Only warnings with numbers can be disabled. Warning numbers are specified at the end of each message in the list of compilation errors. For example, to disable the following warning:
1: Pointer in an array declaration (518.5)
... you just need to write the following comment in a 4D method, preferably a
COMPILER_xxx method (method compiled first):
The "Compiler" page of the Settings dialog box lets you set parameters related to project compilation. You can directly open this page from the compiler window by clicking on the Compiler Settings button:
This area groups the generic options used during the compilation process.
Generate the symbol file
Generate error file
Used to set the number of passes (code parsing) performed by the compiler and thus the duration of compilation.
- Type the variables: Passes by all the stages that make compilation possible.
- Process and interprocess variables are typed: The pass for typing process and interprocess variables is not carried out. This option can be used when you have already carried out the typing of all your process and interprocess variables either yourself or using the function for automatic generation of compiler methods.
- All variables are typed: The pass for typing local, process and interprocess variables is not carried out. Use this option when you are certain that all the process, interprocess and local variables have been clearly typed.
This setting allows you to select the processor family for which your 4D project must be natively compiled. The 4D compiler can build native code for two processor families:
- Intel/AMD processors (all machines),
- Apple Silicon processors.
Two target options are proposed. The result depends on the processor of the machine on which 4D is running.
|Option||on Windows Intel/AMD||on macOS Intel||on macOS Silicon|
|All processors (Intel/AMD and Apple Silicon)||Code for Intel/AMD|
It is not possible to produce Apple Silicon code on Windows
|Code for Apple Silicon + Code for Intel/AMD|
Two compiled codes will be available
|Code for Apple Silicon + Code for Intel/AMD|
Two compiled codes will be available
|My processor (processor)||Code for Intel/AMD||Code for Intel/AMD||Code for Apple Silicon|
Apple Silicon compiler target requires that the Clang application be installed on your machine. Clang comes with the latest version of Xcode. See the Silicon compiler requirements for more information.
Use this area to set the default type for ambiguous database objects.
- Numeric: Used to force numeric typing in an unambiguous manner, either in real or longint. This will not override the directives you may have set in your project. You can optimize the running of your database by choosing the Longint type.
- Button: Used to force button typing in an unambiguous manner, either in real or longint. This will not override the directives you may have set in your project. This type applies to buttons as well as check boxes, picture buttons, button grids, radio buttons, picture pop-up menus and drop-down lists.
Compiler Methods for...
This area lets you rename the Compiler methods that are generated automatically by the compiler when you click Generate Typing.
Up to 5 compiler methods may be generated; a compiler method is only generated if the project contains the following items:
- Variables: Groups together process variable declarations;
- Interprocess Variables: Groups together interprocess variable declarations;
- Arrays: Groups together process array declarations;
- Interprocess Arrays: Groups together interprocess array declarations;
- Methods: Groups together method parameter declarations (for instance,
You can rename each of these methods in the corresponding areas, but they will always be preceded by the label
Compiler_ (non-modifiable). The name of each method (prefix included) must be no longer than 31 characters. It must also be unique and comply with 4D rules for naming methods.
If you check the Generate the symbol file option in the compiler settings, a symbol file called
ProjectName_symbols.txt is created in the Logs folder of the project during compilation. It is divided into several parts:
List of process and interprocess variables
These two lists contain four columns:
- Names of process and interprocess variables and arrays used in your project. These variables are listed in alphabetical order.
- Type of the variable. Types are set by compiler directive commands or are determined by the compiler based on the use of the variable. If the type of a variable cannot be determined, the column is empty.
- Number of dimensions if the variable is an array.
- Reference to the context in which the compiler established the type of the variable. If the variable is used in several contexts, the context mentioned is the one used by the compiler to determine its type.
- If the variable was found in a database method, the database method name is given, preceded by (M)*.
- If the variable was found in a project method, the method is identified as it has been defined in 4D, preceded by (M).
- If the variable was found in a trigger, the table name is given, preceded by (TM).
- If the variable was found in a form method, the form name is given, preceded by the table name and (FM).
- If the variable was found in an object method, the object method’s name is given, preceded by the form name, table name, and by (OM).
- If the variable is an object in a form and does not appear in any project, form, object method, or trigger, the name of the form in which it appears is given, preceded by (F). At the end of each list, you can find the sizes of the process and interprocess variables in bytes.
When compiling, the compiler cannot determine in which process a given process variable is used. A process variable can have a different value in each process. Consequently, all process variables are systematically duplicated as each new process is launched: it is thus advisable to watch out for the amount of memory that they will take up. Also, keep in mind that the space for process variables is not related to the stack size for the process.
List of local variables
The list of local variables is sorted by database method, project method, trigger, form method, and object method, in the same order as in 4D.
This list is divided into three columns:
- list of local variables used in the method;
- type of the variable;
- number of dimensions if the variable is an array.
Complete list of methods
A complete list of your database and project methods is given at the end of the file with:
- their type (procedure or function returning a value)
- the data types of their parameters and the returned result
- the number of calls
- the Thread Safe or Thread Unsafe property.
This information appears as follows:
Procedure or Function <Method name>(parameter data types): result data type, number of calls, Thread Safe or Thread Unsafe
You can choose whether or not to generate an error file during compilation using the Generate error file option in the compiler settings. The error file is automatically named
projectName_errors.xml and is placed in the Logs folder of the project.
Although the errors can be accessed directly via the compiler window, it can be useful to have an error file that can be transmitted from one machine to another. The error file is generated in XML format in order to facilitate automatic parsing of its contents. It also allows the creation of customized error display interfaces.
The length of the error file depends on the number of errors and warnings issued by the compiler.
The structure of the error file is as follows:
- At the top of the file is the list of errors and warnings, sorted by method and in their order of creation in 4D.
- In the General errors section, all the typing impossibilities and identity ambiguities are grouped together. These errors and warnings are listed using the following format:
- line number in the method (0 indicates general errors)
- warning attribute indicating whether the detected anomaly is a warning (warning="true") or an error (warning="false")
- diagnostic describing the error
If your project does not have any general errors, the file will not have a General errors section.
An error file may contain three types of messages:
Errors linked to a specific line: these errors are displayed in context — the line in which they were found — with an explanation. The compiler reports this type of error when it encounters an expression in which it sees an inconsistency related to data type or syntax. In the compiler window, double–click on each error detected in order to open the method concerned directly in the 4D Method editor, with the line containing the error highlighted.
General errors: These are errors that make it impossible to compile the project. There are two cases in which the compiler reports a general error:
- The data type of a process variable could not be determined.
- Two different kinds of objects have the same name.
General errors are so named because they cannot be linked to any specific method. In the first case, the compiler could not perform a specified typing anywhere in the project. In the second, it was unable to decide whether to associate a given name with one object rather than with another.
- Warnings: Warnings are not errors. They do not prevent the project from being compiled, but simply point out potential code errors. In the compiler window, warnings appear in italics. Double-click on each warning to open the method concerned directly in the 4D Method editor, with the line containing the warning highlighted.
The code generated by the 4D compiler automatically checks that every access to an array element or a character reference is done within the actual range of array elements or string characters. Out of range accesses will provoke runtime execution errors.
In some cases, you might prefer range checking not to apply to certain parts of the code that are considered to be reliable. More particularly, in the case of loops that are repeated a great number of times, and when running the compiled database on older machines, range checking can significantly slow down processing. If you are absolutely certain that the code concerned is reliable and cannot cause system errors, you can disable range checking locally.
To do this, you must surround the code to be excluded from range checking with the special comments
//%R- comment disables range checking and
//%R+ enables it again:
// %R- to disable range checking ... //Place the code to be excluded from range checking here // %R+ to enable range checking again for the rest
4D contains two compilers:
- a "classic" compiler, used to compile native code for Intel/AMD processors;
- a Silicon compiler, used to compile native code for Apple Silicon processors.
The classic compiler can be used on any platform, while the Silicon compiler can only be used on a Mac machine:
|Compile for Windows||Compile for Intel Mac||Compile for Silicon Mac|
|On Intel Mac||✓||✓||✓|
|On Silicon Mac||✓||✓||✓|
Both compilers are integrated into 4D. The appropriate compiler is automatically selected depending on the compilation target option.
The classic compiler generates native compiled code for Intel/AMD processors on any machines. It does not require any specific configuration.
Resulting compiled code is stored in the DerivedData folder of the project.
The Silicon compiler generates native compiled code for Apple Silicon processors, such as Apple M1.
Resulting compiled code is stored in the Libraries folder of the project.
- Apple machine: The Silicon compiler can only be run from an Apple machine.
- 4D Project architecture: The Silicon compiler is only available for 4D developments using project architecture.
- Xcode or Developer Tools: The Silicon compiler calls the Clang open-source macOS compiler to compile the project from C++ code at the second step of compilation. clang requires Apple native libraries, which are provided by either the Xcode or Developer Tools package.
- If you already have Xcode or Developer Tools installed on your computer, you only need to make sure that its version is compliant with 4D requirements.
- If you do not have any of these tools installed on your computer, you will need to download one of them from the Apple Developer web site.
We recommend to install Xcode, which is quite simple to install. You can decide to install Developer Tools which is more compact, however its installation is a little more complex.
In any cases, the 4D Silicon compiler will warn you if your configuration does not comply with its requirements.
The Silicon compiler is incremental, which means that:
- During the very first compilation, all 4D methods are compiled. This step could take a certain time. However it only occurs once.
- During all subsequent compilations, only new or modified methods are processed, thus reducing drastically the compilation time.